From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <52EBAE26.8050901@xenomai.org>
Date: Fri, 31 Jan 2014 15:07:34 +0100
From: Philippe Gerum <rpm@xenomai.org>
MIME-Version: 1.0
References: <52EBA6D0.2010208@siemens.com>
In-Reply-To: <52EBA6D0.2010208@siemens.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai] forge/cobalt: Do we need to wrap all POSIX calls for
 non-POSIX skins?
List-Id: Discussions about the Xenomai project <xenomai.xenomai.org>
List-Unsubscribe: <http://www.xenomai.org/mailman/options/xenomai>,
 <mailto:xenomai-request@xenomai.org?subject=unsubscribe>
List-Archive: <http://www.xenomai.org/pipermail/xenomai/>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-request@xenomai.org?subject=help>
List-Subscribe: <http://www.xenomai.org/mailman/listinfo/xenomai>,
 <mailto:xenomai-request@xenomai.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>, Xenomai <xenomai@xenomai.org>

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.