Jan Kiszka wrote:
> Philippe Gerum wrote:
>> Jan Kiszka wrote:
>>> Hi Philippe,
>>> I noticed you fixed the libtool warning during xenomai build - by
>>> linking the testsuite statically... :-/ This is just a workaround and
>>> doesn't help external users.
>> Yes, it's clearly hacky-patchy, however, I don't see how this would
>> impact external users (yet)?
> Those who also use libtool for their apps...
>>> Isn't the reason for this warnings that "-module" in every skin
>>> Makefile.am? At least, removing it also fixes external apps. Do we need
>>> it? I don't think so: -module is for preparing dlopen usage, but who
>>> will use it with skin libs?
>> E.g. People who need to do late binding from some interpreter engine to
>> the routines defined by those APIs.
> Well, then we may better hack the related *.la files when installing
> them ("shouldnotlink=no"). I must confess that I still don't understand
> the reason behind this, but it seems that this warning is really useless
> at least on Linux.

And this is an attempt to silence them at least for the installed

--- src/skins/native/Makefile.am        (revision 612)
+++ src/skins/native/Makefile.am        (working copy)
@@ -20,3 +20,9 @@
 libnative_la_CPPFLAGS = \
        @XENO_USER_CFLAGS@ \
+       for la in $(lib_LTLIBRARIES); do \
+           sed -e 's/shouldnotlink=yes/shouldnotlink=no/'
$(DESTDIR)$(libdir)/$$la > $(DESTDIR)$(libdir)/$$la.patched; \
+           mv $(DESTDIR)$(libdir)/$$la.patched $(DESTDIR)$(libdir)/$$la; \
+       done


Attachment: signature.asc
Description: OpenPGP digital signature

Xenomai-core mailing list

Reply via email to