Subject: Re: [Boost-build] Auto-generating jam files
From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2012-08-16 05:30:25
> I would like to auto-generate a jam file and then have it get used in
> the current running bjam process. I have tried using the SHELL rule
> and/or the response rule like this:
> test =@(../../../Jamroot.jam:E="project test ;â ) ; or test = [
> SHELL âecho âproject test ;â >../../../Jamroot.jamâ ];
> and in both cases the file is generated but the current bjam instance
> does not see it since the following prints nothing until bjam is rerun:
> echo [ glob ../../../*.jam ] ;
> this is also the case with other command like use-project, â¦.
> Is there a way to force bjam to rescan the file system for a particular
I do not think this was intended to be supported in Boost Jam. As I
recall it caches its file system scanning results to avoid costly
rescans. But feel free to play around with it and send in suggested
changes if you find some way to improve it...
What are you trying to do exactly? Perhaps someone can come up with
an alternative solution to the same problem?
Boost library build for exampe does some auto-configuration and
stores its result in project-config.jam (did not research the details
though). In our projects we actually run a wrapper Python script that
generated whatever is needed for the Boost Build/Jam part of the build.
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