[openbeosnetteam] Re: first attempt at a build script (for logging errors)

Cool :) Does it work? What do you get?

david

> Hey all,
>
> following david's request about a build system,
> I made a tiny script.
> after messing with ruby trying to redirect STDOUT and failing miserably
> (only the ruby methods were redirected),
> I resorted to shell scripts.
> basically it only follows what's written in the site, and redirects the
> output of the make commands including errors to a file for each component.
> tested only once, did in 5 minutes.
>
> please, may the shell guru's here perfect it (it's my first useful script)
> if you find a better way, don't hesitate to change, it really is the
> simplest tool i could build.
>
> anyway, check out. don't expect much. it isn't.
> ps: if anyone can do it in perl/python/ruby/whatever do it, since it'll
> help if we want this to be part of a build system.
> ps2: this is not tested yet.
> ps3: change the second line to your net_kit path.
>
> best regards, Kobi.
>
>


----------------------------------------------------------------------------
----


> #!/bin/sh
> net_kit_path="/boot/home/obfs-test/net_kit"
> cd $net_kit_path
> mkdir buildlog
> cd source/server
> make installkernel &> $net_kit_path/buildlog/server.log
> make installdriver &> $net_kit_path/buildlog/driver.log
> cd ../libnet/
> make &> $net_kit_path/buildlog/libnet.log
> make installetc &> $net_kit_path/buildlog/libnetetc.log
> cd ../apps/
> make &> $net_kit_path/buildlog/apps.log
> cd ifconfig/
> make &> $net_kit_path/buildlog/ifconfig.log
> cd ../route/
> make &> $net_kit_path/buildlog/route.log
> cd ../traceroute
> make &> $net_kit_path/buildlog/traceroute.log
> cd ../../server
> make removedriver &> $net_kit_path/buildlog/removedriver.log
> make installdriver &> $net_kit_path/buildlog/installdriver.log
> cd ../apps/ifconfig
> ./ifconfig -a &> $net_kit_path/buildlog/ifconfig-output.log
>

Other related posts: