On Tue, Jun 25, 2002 at 11:34:09PM +1000, Keith Owens wrote:
>
> One other point: kbuild must not assume that it is running on Linux.
> Users must be able to build the Linux kernel from _any_ evironment that
> supports Posix and has a _small_ set of GNU tools. This includes
> Solaris, Cygwin and other host systems. kbuild must not assume that
> non-standard tools such as SCM are available. We do not even assume
> that yacc, lex, loadkeys or Perl are available. These tools may be
> needed for doing development on certain drivers but kbuild must not
> require anything beyond gcc and the standard small set of utilities.
>
> Bottom line: to support add on code and patch sets kbuild has to do the
> work itself.
This does in no way stop you from achiving the same functionality
in a small wrapper script.
Again, do not clobber kbuild with functionality provided by
modern widespread tools.
I could come with other similar examples were we rely on other
tools but could do it in kbuild instead.
Sam
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
