From: Phillip Seaver (phil_at_[hidden])
Date: 2006-09-07 16:24:29
K. Noel Belcourt wrote, on 9/7/2006 4:15 PM:
> Is there some documentation on how to modify Boost build to add new
> command line options? I'd like to know where and how to add options
> when using bjam v2 head. I want to make these command line arguments
> available to the project Jamfiles and would prefer command line
> arguments to requiring users to set environment variables. Something
> bjam --v2 --builddir=/my/derived/files --materialdir=/my/material/
> I've looked at what's done in the Boost distribution but from what I
> can tell, it seems to require modifications to the Jambase, which I'd
> rather avoid if possible. Any ideas?
I know unrecognized options are put in ARGV (I don't recall if
everything on the command-line is), so you can do things like "if
--debug-auto-load in [ modules.peek : ARGV ] ...." (that's an example
from my setup). It doesn't require any modification to boost.build.
There's also an example of an argument with a value in bootstrap.jam:
"local build-system = [ MATCH --build-system=(.*) : $(ARGV) ] ;"
Hope this helps!
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk