C++ static library spaghetti

Asked May 12 '16 at 17:56

Active May 13 '16 at 09:02

Viewed 146 times

Suppose I have a first library called libA. I have 2 versions of libA. The first version is staticly linked in a project called libB.

I have another project which is an executable that contains libA (other version) and libB.

libB needs an older version of libA.

My question is: what will happen when I call a function in libA? How does the compiler know which libA version to call?

edited May 13 '16 at 09:02

Johann Gerell

asked May 12 '16 at 17:56

testpresta

3

I would expect the linker to complain about duplicate symbols. – drescherjm May 12 '16 at 18:02
@drescherjm: Depending on the linker, there may be no errors. Static libraries are just containers of object files, from where they are picked as needed. If every undefined symbol is satisfied by the objects in one lib, then the other may never be linked in and no duplicate error would happen. – rodrigo May 12 '16 at 18:08
Static libraries do not depend on each other. Make a real example and better try to build it before asking here. – Ivan Aksamentov - Drop May 12 '16 at 18:10
3

I think there's no way to solve your problem using static linking, at least with the versions of C++ I'm familiar with. – Mark Ransom May 12 '16 at 18:47
1

Is `libB` actually *dynamically* linked to the executable? I.E. is it a DLL? – Mark Ransom May 12 '16 at 19:29
No, in fact it is two versions of opencv for iOS. It is a .a library – testpresta May 12 '16 at 19:54
i link everything staticly – testpresta May 13 '16 at 19:55

0 Answers0