On Fri, 18 Nov 2005 10:57:04 +1100
Luke Mewburn <lukem@NetBSD.org> wrote:

> On Thu, Nov 17, 2005 at 11:02:57AM +1000, George Michaelson wrote:
>   | 
>   | I still make my kernel by hand, in the live code tree.
>   | 
>   | I would like to make my kernels in the build process, preferably
> in the | OBJ tree.
>   | 
>   | is this doable/sensible?
>   | 
>   | right now, I do:
>   | 
>   | $ cat ~/bin/makeBSD 
>   | #!/bin/sh
>   | 
>   | cd /usr/src
>   | nice ./build.sh -u -x -M /data/Build/obj -T /data/Build/tools
> build \ |         > /var/tmp/build.log 2>&1 & tail
> -f /var/tmp/build.log | $ 
>   | 
>   | where /usr/src is a RO mount of the src hierarchy
>   | (from /data/NetBSD/src, which is where I make kernels by hand)
> 
> Add after "build" argument to build.sh, add
> 	kernel=/path/to/MYKERNELCONFIG
> releasekernel=/path/to/MYKERNELCONFIG
> 
> If you don't provide a path to MYKERNELCONFIG it will be searched
> for in sys/arch/${MACHINE}/conf.
> 
> For that matter, I recommend using "distribution" instead of "build",
> and I also add "sets" and "sourcesets" as well...

Can you explain why? build makes a destdir.${ARCH} for me, which I can
put in-place via (single user) 

(cd /data/Build/obj/usr/src/destdir.${ARCH}; \
 tar cBpf - . | (cd /; tar --unlink -xBpvf -)

what does sets/sourcesets give me?

thanks for the rest of the clue-bat hit! I will amend my script and see
how this goes. (for the kernel build)

-George

> 
> cheers,
> Luke.


-- 
George Michaelson       |  APNIC                 
Email: ggm@apnic.net    |  PO Box 2131 Milton    
Phone: +61 7 3858 3150  |  QLD 4064 Australia    
  Fax: +61 7 3858 3199  |  http://www.apnic.net