Indication of Successful Build

[Russell Haley]

Thanks for the input Mark.

I'm currently looking into the cross build script on the developers
wiki, as well as considering updating crochet to use the u-boot ports
and adding hummingboard to it. I'm going to take all these suggestions
and see what I can come up with. In my mind it wouldn't be hard to use
the return codes indicated by Boris to create a running log of make
results and copy successful outputs to a different directory. What
raises my concern is that I can't be the first person to ever come up
with this idea, so where are all the other attempts at this? In my
mind that means I'm either way ahead of the curve (not) or I am going
down the wrong path and there is something else to this I haven't
considered.

Anyway, I keep telling myself to get on with my own project, but there
is just so much fun stuff to play with down in the guts of FreeBSD! I
was just trying to get booting from NFS to work. lolz. Okay, down the
rabbit hole...

Thanks,

Alice (Russ)

On Wed, Apr 6, 2016 at 12:13 PM, Mark Millard <markmi at dsl-only.net> wrote:
> I use script to make a typescript/log file and keep the log file for as long as I care. So, for example, the script use in:
>
>> # more ~/sys_build_scripts.powerpc64-host/make_powerpc64vtsc_nodebug_incl_clang_xtoolchain-powerpc64-host.sh
>> script ~/sys_typescripts/typescript_make_powerpc64vtsc_nodebug_incl_clang_xtoolchain-powerpc64-host-$(date +%Y-%m-%d:%H:%M:%S) \
>> env __MAKE_CONF="/root/src.configs/make.conf" SRC_ENV_CONF="/root/src.configs/src.conf.powerpc64-xtoolchain.powerpc64-host" \
>> MAKEOBJDIRPREFIX="/usr/obj/xtoolchain/powerpc.powerpc64" \
>> make $*
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"