Re: kbuild-2.5

[Keith Owens <kaos@ocs.com.au>]

On Thu, 01 Nov 2001 11:19:02 +0000, 
David Howells <dhowells@redhat.com> wrote:
>Okay... for users of emacs, here's an elisp function that looks to see if it's
>in a subdirectory of a kernel tree (and if so whether it's kbuild or
>traditional), and if so invents an appropriate command line for compiling just
>in that subdir:-) Otherwise it just falls back to the usual compile function.
>(defun kernel-compile ()
>....
>	  (if (and
>	       (file-readable-p (concat curdir "/COPYING"))

Won't work with separate source and object trees in kbuild 2.5.

  export KBUILD_SRCTREE_000=/build/kaos/2.4.13-kbuild-2.5
  export KBUILD_OBJTREE=/build/kaos/object-2.4.13
  cd /anywhere/you/like
  make -f $KBUILD_SRCTREE_000/Makefile-2.5

If you define the kbuild tree variables then you can be in any
directory when you issue the make command.  If you are using shadow
trees then you can be in a sparse source tree which only contains of
the files.

>	      ;; determine whether using kbuild or not
>	      (if (file-readable-p (concat curdir "/scripts/shadow.pl"))

grep CONFIG_KBUILD_2_5 .config is better, you can still build using
kbuild 2.4 even after applying the 2.5 patch.  The presence of a kbuild
2.5 file is not definitive.  Of course the .config is in $KBUILD_OBJTREE
which might not be the current directory.