From: Jan Kiszka <jan.kiszka@siemens.com>
To: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Default options in the debian package
Date: Fri, 19 Apr 2013 14:48:58 +0200 [thread overview]
Message-ID: <51713D3A.7050205@siemens.com> (raw)
In-Reply-To: <201304191346.38739.leo@alaxarxa.net>
On 2013-04-19 13:46, Leopold Palomo-Avellaneda wrote:
> Hi,
>
>
> in the last days we have had a thread in the orocos-list [1] about the
> convenience to have activated the option (enable-dlopen-skins) in xenomai to
> use it with orocos properly.
>
> I don't know exactly what does it means. The configure says:
>
> --enable-dlopen-skins Disable TLS features and automatic main thread
> mapping by the POSIX skin to allows dlopen'ing
> Xenomai libs. [default=no]
>
>
> I would like to know the implications of have activated this option by default
> in the debian package (at least) . It could be possible? Implies to many
> things?
Well, setting that feature extends the number of use cases for which the
debian package can be used as-is, namely loading skin libraries or other
libraries that require a skin lib via dlopen. We depend on this feature
here, thus carry a local patch against the debian rules, but so far I
thought that this is far from being a common requirement. Does Orocos
have a dynamic plugin concept?
The downside of make the feature default is a micro-performance
degradation (likely not an issue) and the lacking auto-shadowing of the
main thread when using POSIX skins. The latter is a behavioral change
that existing applications may depend and, thus, notice when updating to
the next Xenomai package version.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-04-19 12:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 11:46 [Xenomai] Default options in the debian package Leopold Palomo-Avellaneda
2013-04-19 12:48 ` Jan Kiszka [this message]
2013-04-19 19:06 ` Gilles Chanteperdrix
2013-04-20 6:04 ` Michael Haberler
2013-04-20 8:19 ` Jan Kiszka
2013-04-20 15:14 ` Gilles Chanteperdrix
2013-04-20 15:18 ` Jan Kiszka
2013-04-20 15:21 ` Gilles Chanteperdrix
2013-04-20 15:27 ` Jan Kiszka
2013-04-20 15:30 ` Gilles Chanteperdrix
2013-04-22 7:11 ` Jan Kiszka
2013-04-22 11:37 ` Gilles Chanteperdrix
2013-04-22 13:42 ` Jan Kiszka
2013-04-22 18:57 ` Gilles Chanteperdrix
2013-04-23 8:21 ` Jan Kiszka
2013-04-23 11:20 ` Gilles Chanteperdrix
2013-04-23 12:22 ` Jan Kiszka
2013-04-23 12:40 ` Philippe Gerum
2013-04-23 12:55 ` Jan Kiszka
2013-04-23 13:03 ` Philippe Gerum
2013-04-22 15:15 ` Jeff Webb
2013-04-22 7:18 ` Leopold Palomo-Avellaneda
2013-04-22 11:42 ` Gilles Chanteperdrix
2013-04-22 14:54 ` Leopold Palomo-Avellaneda
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=51713D3A.7050205@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=leo@alaxarxa.net \
--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.