Boost logo

Boost-Build :

Subject: Re: [Boost-build] Recursive bjam (or equivalent) solution?
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-01-29 10:40:35

On Friday 23 January 2009 23:38:39 David Abrahams wrote:
> Hi,
> Our literate programming framework allows us to generate a Jamfile and a
> bunch of source files from an input .rst file. For example, I might
> $ python ~/src/boost/tools/litre/ \
> ~/src/boost/libs/parameter/doc/index.rst \
> --dump_dir=~/src/boost/libs/parameter/test/literate
> to generate a project in ~/src/boost/libs/parameter/test/literate. I
> can then
> $ cd ~/src/boost/libs/parameter/test/literate
> $ bjam
> To run all the tests. What I'd really like is for that directory to get
> extracted and tested during the regular Boost test suite, so I don't
> have to check in these generated files and keep them up-to-date with the
> actual docs. Is there a way?

Recursive invocation of bjam, or any way to intervleave parsing of Jamfiles
and running of commands, is not supported right now. However, by looking
at the command you gave, I wonder if you can either:

- Use SHELL builtin to always run this command when status/Jamfile.v2 is read
- Use a notfile target in status/Jamfile.v2, say 'prepare' and arrange for the
testing framework to build said target before actual test run

- Volodya

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at