From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2007-01-01 09:13:05
Jorge Suit Perez Ronda wrote:
>> I think it's a good base to extend and customize, so I'm going to
>> use it for my further experiments. For now, I post it as config.jam
>> file into my SVN playground:
>> I hope you don't mind, do you?
> for me is OK, I will update config.jam from that repository, also if
> I had any changes I'll ask you about how to merge it.
OK, if this utility won't get into the Boost.Build, I keep it there.
>> BTW, do you have any plans to extend and publish your module
> what would be nice is that config.jam be accepted and enhanced by the
> Boost-Build community, any comment from the experts would be
Yes, that would be great.
Back to the config.jam, are you going to keep file-base only configuration?
I mean config <pkg> specified in your prj-config.jam.
Next step I'd like to achieve is to externalize --with-<pkg> options.
I also wonder if it's possible to have those options printable from
bjam, for instance when user runs
bjam --help config
then all options supported by particular project would be generated
dynamically based on prj-config.jam and printed:
In your case it would output:
+ some descriptions.
Definition in file like prj-config.jam could be used to control "What
options are supported by the project".
Next, options are passed in bjam's command line.
For now, I only know how to check if given options was passed to bjam
in command line:
if ( --with-$(pkg) in [ modules.peek : ARGV ] )
# option passed, check if $(pkg) is supported and configure it
It's nothing serious, just experimenting after 2 days of Jaming.
-- Mateusz Loskot http://mateusz.loskot.net
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