From: Philippe Gerum <rpm@xenomai.org>
To: Frederik Bayart <frederik_bayart@yahoo.co.uk>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xenomai-3.0-rc5 : binding named semaphores from external process
Date: Wed, 29 Jul 2015 14:28:58 +0200 [thread overview]
Message-ID: <55B8C70A.9010107@xenomai.org> (raw)
In-Reply-To: <279611839.4860606.1438170528832.JavaMail.yahoo@mail.yahoo.com>
On 07/29/2015 01:48 PM, Frederik Bayart wrote:
> In attachment my latest version of stest.c to be sure, there are only small modifications.
>
If __XENO_COMPAT__ is enabled, that should mean that you built your
application with --[skin=]native, which automatically enables backward
compat mode from {lib, include}/trank, to the new alchemy API.
In this case, you don't need to test this symbol for picking the proper
include files, these are available from include/trank/native, which
xeno-config points you at.
Obsolete definitions like T_FPU will be found in those compat headers.
--
Philippe.
next prev parent reply other threads:[~2015-07-29 12:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 13:37 [Xenomai] xenomai-3.0-rc5 : binding named semaphores from external process Frederik Bayart
2015-07-14 9:53 ` Philippe Gerum
2015-07-15 12:45 ` Frederik Bayart
2015-07-16 15:35 ` Philippe Gerum
2015-07-28 15:19 ` Frederik Bayart
2015-07-29 10:12 ` Philippe Gerum
2015-07-29 11:48 ` Frederik Bayart
2015-07-29 12:20 ` Philippe Gerum
2015-07-29 12:28 ` Philippe Gerum [this message]
2015-07-29 12:48 ` Philippe Gerum
2015-07-29 12:56 ` Philippe Gerum
2015-07-29 15:14 ` Frederik Bayart
2015-07-29 18:27 ` Philippe Gerum
2015-07-29 18:42 ` Philippe Gerum
2015-07-30 14:28 ` Frederik Bayart
2015-07-30 15:08 ` Frederik Bayart
2015-07-30 16:10 ` Philippe Gerum
2015-07-31 17:54 ` Frederik Bayart
2015-08-01 7:59 ` Philippe Gerum
2015-08-01 8:43 ` Philippe Gerum
2015-08-03 9:59 ` Frederik Bayart
2015-07-30 15:58 ` Philippe Gerum
2015-07-30 16:36 ` Philippe Gerum
2015-07-31 16:04 ` Frederik Bayart
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=55B8C70A.9010107@xenomai.org \
--to=rpm@xenomai.org \
--cc=frederik_bayart@yahoo.co.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.