From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Built-in libxenomai dependency
Date: Wed, 01 Feb 2012 16:25:51 +0100 [thread overview]
Message-ID: <4F29597F.8050500@domain.hid> (raw)
In-Reply-To: <4F2957A0.6040806@domain.hid>
On 2012-02-01 16:17, Gilles Chanteperdrix wrote:
> On 02/01/2012 03:37 PM, Jan Kiszka wrote:
>> 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").
>
> It allows xeno-config result to work both with dynamic and static
> libraries. Static libraries have no dependency system, so, when linking
> a program whith libnative.a for instance, without libtool, you still
> have to link it with libxenomai.a.
OK, part two could stay, but the dependencies should still be added to
the skin libs - if possible.
>
> How come you can not dlopen libnative.so, dlopening libxenomai.so before
> does not work?
Dependencies of libnative on libxenomai are not resolved when you open
the former even if the latter is already loaded. Maybe you can do this
by pulling in all required symbols one by one manually, haven't tried
yet. But that would at least be unhandy.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-02-01 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 14:37 [Xenomai-core] Built-in libxenomai dependency Jan Kiszka
2012-02-01 15:17 ` Gilles Chanteperdrix
2012-02-01 15:25 ` Jan Kiszka [this message]
2012-02-01 15:38 ` Gilles Chanteperdrix
2012-02-01 15:50 ` Jan Kiszka
2012-02-01 20:21 ` Gilles Chanteperdrix
2012-02-07 16:19 ` Gilles Chanteperdrix
2012-02-07 16:22 ` Jan Kiszka
2012-02-07 16:28 ` Gilles Chanteperdrix
2012-02-07 16:36 ` Jan Kiszka
2012-02-08 18:24 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F29597F.8050500@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.