Re: C++ (g++) linker error linking dependent static libraries to
create executable
On Jan 25, 6:27 pm, "sriram.sundarara...@gmail.com"
<sriram.sundarara...@gmail.com> wrote:
I got this....
blah/lib2/libB.a(libB.o): In function `ZN1B1aESs':
blah/lib2/libB.cpp:9: undefined reference to `A::printB(std::string)'
blah/lib2/libB.a(libB.o): In function `ZN1B1bEi':
blah/lib2/libB.cpp:15: undefined reference to `A::printA(int)'
collect2: ld returned 1 exit status
make: *** [debug/main.exe] Error
I am sure
1. I used my -L and -l options right
You didn't in the example.
You mean I should've used -lA and -lB instead of specifying the paths
to libA.a and libB.b?
No, I mean you should have specified libB before libA.
I think they are equivalent.
They are IF the -L flags are set correctly, and IF the libraries
are names correctly. Almost, anyway: if you specify -lA, and
there is both a libA.a and a libA.so in the same directory,
which one you'll get will depend on various compiler options
(but by default is the .so). If you specify <path>/libA.a, then
you'll get the statically linked one.
In fact, I almost always use the pathname (as you did in your
example) for my own libraries, leaving -l for libraries which
the compiler should search in "standard places".
[...]
(FWIW, I once used a linker which not> only processed the
libraries in order, but processed each
library sequentially. Even within a library, you had to do a
topological sort on the dependencies to ensure the order.)
Your pain was far greater than mine :)!
It did encourage one to avoid cyclic dependencies, which isn't
bad:-). And there was a tool to order the libraries. But yes, it
was a bit drastic.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34