Subject: Re: Suggested addition to build.sh
To: Todd Vierling <email@example.com>
From: David Brownlee <firstname.lastname@example.org>
Date: 05/17/2002 17:05:56
On Fri, 17 May 2002, Todd Vierling wrote:
> On Fri, 17 May 2002, Frederick Bruckman wrote:
> : > It would be much nicer to be able to tell them to run
> : > './build.sh -K FUBAR', which run the above, then displays:
> : > "The FUBAR kernel is now in \
> : > ../sys/arch/$MACHINE/compile/$KERNCONFNAME/netbsd"
> This can probably be implemented. I'll look into it.
> : That would be nice. While we're wishing, I'd really like to see a
> : top-level target to build a bootable sysinstall kernel with the
> : ramdisk and everything.
> Unfortunately, the distrib directories are nowhere near uniform across
> platforms, so "where should it go build?". Doubly so, it needs an include
> and lib populated $DESTDIR in order to work correctly.
It could build 'instkernel' if present, or fail out if not.
In an ideal world every port should have that target.
If there are more than one inst kernel then instkernel should
build all of them.
Any such target would run the 'make includes' and 'make && make
install' in lib as necessary. Possible force -D usage with it.
David/absolute -- www.netbsd.org: No hype required --