From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: Oops, I broke something
Date: Fri, 06 Jan 2006 13:38:36 +0100 [thread overview]
Message-ID: <43BE64CC.2020504@domain.hid> (raw)
In-Reply-To: <43BE5E3E.1060208@domain.hid>
Jan Kiszka wrote:
> Hi Philippe,
>
> my RTDM header "optimisation" broke the compilation of
> testsuite/latency. I need an extra link for the userspace compilation
> inside xeno now. Please apply this patch
>
> --- configure.in (Revision 372)
> +++ configure.in (Arbeitskopie)
> @@ -348,6 +348,8 @@
>
> base=include
> AC_CONFIG_LINKS([src/include/xenomai:$base])
> +base=rtdm
> +AC_CONFIG_LINKS([src/include/$base:include/$base])
> base=asm-$XENO_TARGET_ARCH
> AC_CONFIG_LINKS([src/include/asm/xenomai:include/$base])
> base=asm-generic
>
> and run bootstrap. Sorry.
>
> 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>?
>
Nope, people writing apps should not have to handle our internal issues,
asking them to prefix with xenomai/ is not an option.
> Jan
--
Philippe.
prev parent reply other threads:[~2006-01-06 12:38 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
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 [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=43BE64CC.2020504@domain.hid \
--to=rpm@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.