help me use this script ...

[Ian Lepore]

On Tue, 2012-10-23 at 00:05 -0700, Jack Mc Lauren wrote:

[Note: missing original quotation context here, the quote below is
mostly something I said/posted...]

> I'm on dangerous ground here... if I demonstrate too much knowledge of
> our crazy-complex build system, suddenly I'm going to find that I'm the
> new buildmeister.  :)  But, it didn't take me too long to find where we
> do this stuff...
> 
> We have a variable that contains a list of dirs under
> build-chroot/usr/src and in our script that populates the image we have
> this loop:
> 
>         for i in ${FreeBSDProgramDirs}; do
>             echo "==> $i"
>             (cd $i && eval env ${mkenv} ${mkcmd} INSTALL=install \
>                 NOINSTALLLIB=yes NO_INSTALLLIB=yes install)
>         done
> 
> So I gather we never do a full installworld at all, we just run that
> loop instead.  Here's our basic list; we add to this list for some
> products, others need just this stuff.
> 
> FREEBSDMIN+= \
>     bin/cat \

> [snip large dir list here]
> -- Ian
> ========================================================================================
> Thank you friends ...
> how can use this loop ? could explain it in a nanobsd.sh file please ??

I can't really help any further... I've never used nanobsd.  The only
thing I know about it is a vague sense that it does cross-building
within a chroot, and that's basically the same concept as our build
system at work uses, but with a completely different implementation.

The snippet of script I posted is run from within our chroot
environment, after having copied parms such as that list of dirs into
chroot/tmp/whatever (so that it's accessible to the script inside the
chroot as /tmp/whatever), and then the name of the file holding the
parms is passed to the in-chroot install script via an env var.  The
install script itself is also copied into chroot/tmp from the outside
build script.

-- Ian