On 25/05/14 10:03, Justin Cormack wrote: >> I think the intention was that there are variables which are probed and >> set by buildrump.sh (EXTRA_FOO) and ones which can be specified in the >> environment and will be picked up by rumpmake when it is run >> (BUILDRUMP_FOO). >> >> Hmm, so the intention was that BUILDRUMP_FOO would not be used by >> [directly] by buildrump.sh... might have to work on the names of those >> variables ;) > > The problem is that some of the changes you can make with flags affect > the choices that buildrump.sh has to make, eg ABI selection for mips. > You can add more options for buildrump.sh to work around this of > course but it gets messier. Will have a think about the options...
We could just agree that rumpmake picking things up from the env is silly since there's no way to negate parameters. I don't really like buildrump.sh picking up random things from the env, so we could add a parameter like -F for something like -F CPPFLAGS=foo -F CFLAGS=bar, and those would be internally used by buildrump.sh when probing. The whole subject is quite full of complex details and should be solved once and for all one of these days. Is there any way you can move forward with a hack, e.g. hacking buildrump.sh to use BUILDRUMP_FOO internally? Obviously that would be an unsupported/documented hack, but should work for the time being. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
