I've got three libraries, A, B, C. C uses symbols from B, and B uses
symbols from A.
When I build these libraries as static libraries (libA.a, libB.a, and
libC.a), the linker is perfectly happy to produce libC.a even if I
haven't told it about B. It seems that all that matters is, when I'm
Hi,
Convey, Christian J CIV NUWC NWPT wrote:
I've got three libraries, A, B, C. C uses symbols from B, and B uses
symbols from A.
When I build these libraries as static libraries (libA.a, libB.a, and
libC.a), the linker is perfectly happy to produce libC.a even if I
haven't told it about
When my project contains two libraries, where one depends on the other...
Are there any reasons for, or against, calling th
TARGET_LINK_LIBRARIES command to express that dependency?
Does the answer change depending on whether zero, one, or both of them
are static vs. dynamic libraries?
Thanks,
On 8/7/07, Christian Convey [EMAIL PROTECTED] wrote:
When my project contains two libraries, where one depends on the other...
Are there any reasons for, or against, calling th
TARGET_LINK_LIBRARIES command to express that dependency?
Does the answer change depending on whether zero, one, or