g++ and static libraries / use .a instead of .so

[Cygnus]

Hi. I have a minor problem. Do you know how to make g++ -l flags use the .a library instead of the .so ones when both are available ? Hardcoding the path works fine, but I assume there is a better way.

In short; if you have liba.so and liba.a and specify -la to g++ it seems to pick up liba.so. Can you make it prefer .a instead ?

[LaRoza]

Hi. I have a minor problem. Do you know how to make g++ -l flags use the .a library instead of the .so ones when both are available ? Hardcoding the path works fine, but I assume there is a better way.

In short; if you have liba.so and liba.a and specify -la to g++ it seems to pick up liba.so. Can you make it prefer .a instead ?

.a is for static linking and .so is for shared libraries.

Look up on how to static link (man gcc)

[Cygnus]

.a is for static linking and .so is for shared libraries.

Look up on how to static link (man gcc)

The static linking works fine when using full path to the .a file, I just want to know if there is a flag or setting to make use static linking of a library when you use -l and there are are both .so and .a versions available.

I have already looked in man gcc of course but not yet found anything.

[gnusci]

If the library name is liba.a, you should get the linking adding the flag -static -la.

EDITED

[supirman]

pass the option -Wl,-Bstatic to g++,

g++ [your other stuff] -Wl,-Bstatic -la 

[Cygnus]

Thanks for the replies. I had earlier tried with the -static flag but it only gave me errors. I now continued to investigate that and I found that this combination worked:

-static-libgcc -Wl,-static -la

-static must be passed to the linker as supirman suggested with -Wl but I also needed -static-libgcc or I ran into the error described at this link: <debian-gcc>.

[nvteighen]

But, wait: Won't -static static-link all libraries? If you want to static-link only some libraries, probably using the whole path to the .a file is the best solution (remember: A .a file is just a bunch of .o files, so both are linked the same way).

[Cygnus]

But, wait: Won't -static static-link all libraries? If you want to static-link only some libraries, probably using the whole path to the .a file is the best solution (remember: A .a file is just a bunch of .o files, so both are linked the same way).

Note that -Wl,-static goes to the linker. It only affects libraries after it. From man ld:

You may use this option multiple times on the command line: it affects library searching for -l options which follow it.

[drunken_sapo]

isn't there any elegant way to say to the compiler: "prefer static libraries"? If you are linking against dozens of libraries or you don't know (nor want to find out) which ones are static or shared, using the order to specify it really is not an option.
No one knows any workaround for this?

[dribeas]

Hi. I have a minor problem. Do you know how to make g++ -l flags use the .a library instead of the .so ones when both are available ? Hardcoding the path works fine, but I assume there is a better way.

In short; if you have liba.so and liba.a and specify -la to g++ it seems to pick up liba.so. Can you make it prefer .a instead ?

Your question has already been answered, just a hint: be careful with static library linking, as they are dependent on the order in which you type the link/compiler command line. An static library can depend only on symbols defined previously in the command line.

David