So when I understand you correct you don't want to give the option
"-lrt" again when building progbar which links against libfoo (which
itself already was linked against librt)?
In this case building libfoo needs to use this statement for linking:
-Wl,-whole-archive -lrt -Wl,-no-whole-archive
No
Okay, Robert already answered but...
On 16/07/2013 15:56, Steffen Sledz wrote:
> FOO_LDFLAGS="-L$with_libfoo_path/lib -lfoo"
[...]
> progbar_LDFLAGS = $(FOO_LDFLAGS)
This is simply wrong, whether or not it works after adding LT_INIT.
-lfoo is a library not an LDFLAG.
It should be passed t
On 16.07.2013 17:47, Robert Boehne wrote:
> That said - It looks to me like you're not *using* libtool to do your linking.
> Libtool's la files contain all the dependencies that a library needs.
> This is a big help when using static archives because they need
> to have everything listed in the pro
Steffen,
I would suggest asking questions about Libtool on a libtool mailing list.
That said - It looks to me like you're not *using* libtool to do your
linking.
Libtool's la files contain all the dependencies that a library needs.
This is a big help when using static archives because they nee
Sorry, if this is a faq, but i didn't found a clear answer searching around.
Given situation: We have a library called e.g. libfoo which uses e.g. mq_open
from librt. Than we have a program e.g. called progbar which requires libfoo
(and therefor also librt).
Our current solution looks like this
