[EMAIL PROTECTED] wrote:
>
> On Tue, Feb 15, 2000 at 11:30:06AM +0000, Stuart Hughes wrote:
> > [EMAIL PROTECTED] wrote:
> > >
> > > On Mon, Feb 14, 2000 at 05:00:22PM -0500, Paul Koning wrote:
> > > > I noticed that (at least in 3.0) there's a config symbol for RTLinux.
> > > > But it isn't being used in the usual way -- the RTL code dropped in by
> > > > the patches isn't controlled by #ifdef CONFIG_RTLINUX (with one or two
> > > > exceptions) -- and it isn't a configuration dialog question.
> > >
> > > CONFIG_RTLINUX is useful to export that it is a RT kernel. But once the
> > > patch is installed, there is no point in pretending it's not a RTLinux kernel
> > > so a config option is useless.
> >
> > Hi Victor,
> >
> > For me having a CONFIG_RTL is very useful as I can then
> > #include <linux/config.h>
>
> I don't get it. CONFIG_RTLINUX tells you that it was configured for
> RTLinux. If you have a variant, then presumably you config something
> else. Am I missing something?
No, except CONFIG_RTL makes a positive id that RTL is patched and in the
kernel. This is an essential piece of information for me (and I think
many others) to make sure that code that is built does the right thing.
One app that I have can work without any RT (for those that only have
standard kernels), so I use this CONFIG to decide how the app should be
built.
Please leave it in if you can.
Thanks, Stuart.
-- [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/
