From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <43BEA171.4010300@domain.hid> Date: Fri, 06 Jan 2006 17:57:21 +0100 From: Philippe Gerum MIME-Version: 1.0 Subject: Re: [Xenomai-core] Re: Oops, I broke something References: <43BE5E3E.1060208@domain.hid> <43BE626A.6000500@domain.hid> <17342.26740.324646.221814@domain.hid> In-Reply-To: <17342.26740.324646.221814@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Jan Kiszka , xenomai-core 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 instead of just ? > > > > 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 While checking the 2.4 builds for ppc and x86, I stumbled upon cases where we do need this fix right now (e.g. benchmark and 16550A drivers). So I will handle this global change right after -rc2 is out. -- Philippe.