On Wed, Jul 26, 2000 at 03:26:53PM -0600, [EMAIL PROTECTED] wrote:
>
> I don't think include files belong in /usr/lib/.
It is common practice for cross-development environments to put
header files in /usr/lib/<arch>/include. Compiling kernel modules
is pretty close to cross-development.
Moving all the realtime-target header files out of /usr/include
removes a lot of potential compilation problems. Using "-nostdinc
-I /usr/lib/realtime/include -I /usr/src/linux/include" is pretty
convenient to get all the right bits, and exclude all the wrong
bits.
> If we have similar include files then a package maintainer or builder that
> uses one of the flavors just needs to change a '-I' line.
>
> } Also, I'd like to see RTAI and RTLinux header files installed
> } into /usr/lib/realtime/include/rtai and .../rtlinux, assuming
> } that the respective maintainers are interested in the required
> } amount of source-compatibility.
(I re-read this, and realized that it might be confusing: I
meant to say "source compatibility between different releases of
a project", not "source compatibility between projects".)
> How about /usr/include/rt_libc/. I like the idea of being able to switch
> around with -I and not changing the source once it's done.
ditto.
> Do what we did, mail hpa or Linus and request a major/minor number. It
>
> } 3. Allocation of a real-time misc device major number.
Um... I think I know *how* to do it. I was asking if people think
there is a sufficient need, and possible alternatives.
dave...
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
