opensubscriber
   Find in this group all groups
 
Unknown more information…

x : xenomai-core@gna.org 1 February 2012 • 10:37PM -0500

[Xenomai-core] Built-in libxenomai dependency
by Jan Kiszka

REPLY TO AUTHOR
 
REPLY TO GROUP




Hi,

don't remember anymore: Is there any subtle reason that prevent a
change like

diff --git a/src/skins/native/Makefile.am b/src/skins/native/Makefile.am
index 39eaaed..4cc8859 100644
--- a/src/skins/native/Makefile.am
+++ b/src/skins/native/Makefile.am
@@ -22,6 +22,9 @@ libnative_la_SOURCES = \
wrappers.c \
wrappers.h

+libnative_la_LIBADD = \
+ ../common/libxenomai.la
+
libnative_la_CPPFLAGS = \
@XENO_USER_CFLAGS@ \
-I$(top_srcdir)/include
diff --git a/src/skins/rtdm/Makefile.am b/src/skins/rtdm/Makefile.am
index 8ad74be..2dc0a90 100644
--- a/src/skins/rtdm/Makefile.am
+++ b/src/skins/rtdm/Makefile.am
@@ -8,6 +8,9 @@ librtdm_la_SOURCES = \
core.c \
init.c

+librtdm_la_LIBADD = \
+ ../common/libxenomai.la
+
librtdm_la_CPPFLAGS = \
@XENO_USER_CFLAGS@ \
-I$(top_srcdir)/include
diff --git a/src/testsuite/latency/Makefile.am b/src/testsuite/latency/Makefile.am
index c772c26..6534df5 100644
--- a/src/testsuite/latency/Makefile.am
+++ b/src/testsuite/latency/Makefile.am
@@ -14,5 +14,4 @@ latency_LDFLAGS = @XENO_USER_LDFLAGS@
latency_LDADD = \
../../skins/native/libnative.la \
../../skins/rtdm/librtdm.la \
- ../../skins/common/libxenomai.la \
-lpthread -lm

i.e. that we let the skin libraries depend on libxenomai and then remove
the explicit dependency from our binaries and the xeno-config output?
Is there some ordering issue again (we have -l<skin> before -lxenomai
in the ldflags).

If possible, this would allow for things like dlopen("libnative.so").

Jan

--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna....
https://mail.gna.org/listinfo/xenomai-core

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.