From: Philippe Gerum <rpm@xenomai.org>
To: Giulio Moro <g.moro@qmul.ac.uk>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] doc for xeno-config skins
Date: Sun, 8 Apr 2018 17:43:05 +0200 [thread overview]
Message-ID: <4da13ab9-1518-f74c-4dea-9f67e392b204@xenomai.org> (raw)
In-Reply-To: <16992f8a-acba-371e-bd48-b515d60978ff@xenomai.org>
On 04/05/2018 03:25 PM, Philippe Gerum wrote:
> On 04/05/2018 01:39 PM, Giulio Moro wrote:
>> Thanks and sorry for overlooking that. I thought if there was some docs on xeno-config it would have been inlined in its source, so that is where I looked for it. I guess the man folder should have been a more obvious choice.
>>
>> Is it correct that calling `xeno-config --skin cobalt` expects you to call, POSIX functions prefixed with `__wrap_` ? Does this mean that the *actual* "Cobalt POSIX interface" consists of __wrap_fn() calls as opposed to fn() calls?
>
> __RT(fn()) and __COBALT(fn()) hide this ugly __wrap prefix inside an
> ugly macro. __STD() keeps consistent with such ugliness for __real calls.
>
>> If yes, is this documented somewhere obvious?
> I kind of figured this out over time by reading
> http://xenomai.org/2014/08/porting-a-linux-application-to-xenomai-dual-kernel/
> and looking at the wrappers files and at the source code, but is it
> stated clearly somewhere?
>
> Of course not. Proper documentation hinders fruitful imagination.
>
>> This is a place where I would have looked for that, for instance: http://www.xenomai.org/documentation/xenomai-3/html/xeno3prm/group__cobalt__api.html .
>>
>
> Makes sense, added to my todo list. This is part of a larger
> documentation work.
>
This commit is an attempt to clarify the matter of symbol wrapping:
http://git.xenomai.org/xenomai-3.git/commit/?id=e28d2631154d26e00715a5ef0f952ceb5df7ef59
--
Philippe.
prev parent reply other threads:[~2018-04-08 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 20:15 [Xenomai] doc for xeno-config skins Giulio Moro
2018-04-05 6:36 ` Philippe Gerum
2018-04-05 11:39 ` Giulio Moro
2018-04-05 13:25 ` Philippe Gerum
2018-04-08 15:43 ` Philippe Gerum [this message]
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=4da13ab9-1518-f74c-4dea-9f67e392b204@xenomai.org \
--to=rpm@xenomai.org \
--cc=g.moro@qmul.ac.uk \
--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.