I think it's probably been done before, but in the last couple days
I've been playing with the kernel build system to this end. (Partly
because it will be useful and partly as an exercise to learn the kbuild
system better.)
My changes so far are a little script that creates the directory
hierarchy and symlinks the Makefiles, a little rearranging of include/
which features a build/ directory for volatile things, and some random
hackery in places like Makefile, Rules.make and scripts/Configure. A
lot of it seems to almost work. `make dep' gave me a little trouble,
since it is so highly optimized for the status quo....
> Won't do you much good: autoconf (and the whole GNU build system)
> does not allow distributed use of a unified source tree (cygnus
> automake allowed that at one point, but is apparently no longer
> maintained).
Am I understanding you correctly? It sounds like you mean
$ tar xzf foo-1.0.tar.gz
$ mkdir foo-obj
$ cd foo-obj
$ ../foo-1.0/configure
$ make
This works fine for all autoconf-based packages I use. Perhaps it
only works with GNU make, I don't know.
> eg one would have to move include/asm-<arch> to <arch>/include/asm
> and get rid of those pesky symlinks. Next one has to think about
> autoconf.h and version.h which have to be created in the obj
> directory and not the src directory (speaking in BSD terms here).
Yeah, those are some of the issues I've hit.
> the resulting Makefiles could be smaller in size and faster in terms
> of processing time (note that gmake is typically slower than pmake
> and has a bigger memory footprint).
OK, here's a question: what kernel build system features are GNU
extensions? I.e. what would need to be reworked for pmake?
-- Peter Samuelson <sampo.creighton.edu!psamuels>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/