Hey all y'all,

Something that has bugged me about buildrump.sh for a long time is that 
it's not obvious which options are used/recorded with which commands. 
For example, "./buildrump.sh -q tools build" will do a quiet build, but 
"./buildrump.sh tools; ./buildrump.sh -q build" will not.  As an example 
of some concrete problems, see the buildnb.sh script in the rumprun 
repository.  So, how to fix this?

On the high level, I'm thinking about two changes:
* adding a "config" command, which will store parameters in a config file
* make all parameters from the config file overridable by command line 
params.  notably, unlike "config", this would not store parameters, just 
use them in the current invocation

The config would be selectable by using -c <configname>.

I'm thinking of making one user-visible change: for simplicity, make the 
config name same as the rumpmake wrapper, so if you want to use 
<configname> when running make manually, you'd just run <configname> 
(cf. "rumpmake").  However, this means that the config would be a 
(-c,-T) tuple.  Since the default for -T is obj/tooldir, it depends on 
the object directory location.  So, to avoid the default value of -T 
depending on -o, I'm planning of changing the default value of -T to 
./tooldir.

If someone has any comments on the above plan, or other concerns they'd 
want to have addressed with the build/config revamp, now's a good time 
to voice them.  I'll be doing the work on the "buildconfig" branch of 
buildrump.sh on github.  It will hopefully be merged at the end of this 
week.

   - antti

------------------------------------------------------------------------------
Android&trade; apps run on BlackBerry&reg;10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users

Reply via email to