From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Re: Oops, I broke something
Date: Fri, 06 Jan 2006 14:56:44 +0100 [thread overview]
Message-ID: <43BE771C.2090005@domain.hid> (raw)
In-Reply-To: <17342.26740.324646.221814@domain.hid>
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > Jan Kiszka wrote:
> > > But this raised the question to me again if we really need the "xenomai"
> > > prefix for all the skin headers /from within xenomai/. Why not doing the
> > > same linking dance for the other skins as well? Or do you also prefer
> > > that user include <xenomai/native/task.h> instead of just <native/task.h>?
> >
> > We need this for building from within the kernel. Other options would
> > require to either alter the Xenomai source tree adding symlinks there,
> > pollute linux/include with symlinks to reach the individual Xeno
> > components, or refer to some external tree that eventually redirects to
> > the Xenomai tree, which is not acceptable in any case.
>
> Maybe we could add EXTRA_CFLAGS=-I$(TOPDIR)/include/xenomai to every
> xenomai kernel makefile
Yes, I would preferably merge that instead of playing with symlinks.
and to the cflags returned by xeno-config for
> kernel-space applications ?
>
There no such support in xeno-config anymore. Kernel module flags and
dependencies now exclusively belong to the kernel build system;
xeno-config is only relevant for building user-space apps.
--
Philippe.
next prev parent reply other threads:[~2006-01-06 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 12:10 [Xenomai-core] Oops, I broke something Jan Kiszka
2006-01-06 12:28 ` [Xenomai-core] " Philippe Gerum
2006-01-06 12:54 ` Gilles Chanteperdrix
2006-01-06 13:56 ` Philippe Gerum [this message]
2006-01-06 17:01 ` Jan Kiszka
2006-01-06 18:38 ` Philippe Gerum
2006-01-06 16:57 ` Philippe Gerum
2006-01-06 12:38 ` Philippe Gerum
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=43BE771C.2090005@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--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.