From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <43BE64CC.2020504@domain.hid> Date: Fri, 06 Jan 2006 13:38:36 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <43BE5E3E.1060208@domain.hid> In-Reply-To: <43BE5E3E.1060208@domain.hid> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: [Xenomai-core] Re: Oops, I broke something List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai-core 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 instead of just ? > Nope, people writing apps should not have to handle our internal issues, asking them to prefix with xenomai/ is not an option. > Jan -- Philippe.