All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] forge/cobalt: Do we need to wrap all POSIX calls for non-POSIX skins?
Date: Fri, 31 Jan 2014 15:07:34 +0100	[thread overview]
Message-ID: <52EBAE26.8050901@xenomai.org> (raw)
In-Reply-To: <52EBA6D0.2010208@siemens.com>

On 01/31/2014 02:36 PM, Jan Kiszka wrote:
> Hi,
>
> was asked why, e.g., xeno-config --skin=alchemy --ldflags returns
> -Wl,@/data/xenomai-forge/inst64/lib/cobalt.wrappers. Is there a
> technical reason? On first glance and after minimal testing, it seems not.
>

There is no technical reason, since all libs are required to use manual 
wrapping for these symbols (e.g. __RT()/__STD()) to keep automatic 
wrapping via the linker optional.

The current assumption is that application code using cobalt-provided 
routines do want such wrapping to take place automatically, for mixing APIs.

OTOH, we could require such applications to mention --posix explicitly 
for enabling this feature. It makes sense either way. We need to ponder 
which one follows the principle of least astonishment.

-- 
Philippe.


  parent reply	other threads:[~2014-01-31 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 13:36 [Xenomai] forge/cobalt: Do we need to wrap all POSIX calls for non-POSIX skins? Jan Kiszka
2014-01-31 13:53 ` Gilles Chanteperdrix
2014-01-31 13:58   ` Jan Kiszka
2014-01-31 14:14   ` Philippe Gerum
2014-01-31 14:07 ` Philippe Gerum [this message]
2014-02-03 13:03   ` Jan Kiszka

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=52EBAE26.8050901@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --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.