From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-04-26 03:20:46
On Wednesday 19 April 2006 14:32, João Abecasis wrote:
> Incidentally, just yesterday I finally ported to bjam+BBv2 a shell
> script I've been using for the same purpose. See attached. You should
> put headers.jam file in the same directory as your Jamfile[.v2] or
> somewhere where Boost.Build can find it (e.g., in BOOST_BUILD_PATH).
> For example, to test the compilation of Boost.Spirit headers, in
> (boost-root)/libs/spirit/test/Jamfile.v2 one could have:
> import headers ;
> import testing ;
> test-suite "spirit.headers"
> : [ headers ../../../boost/spirit ]
> At this point the code is the documentation, but I added some comments
> explaining each function's purpose.
> Perhaps this, or something along the lines of it, could be added to the
> regression tests, to ensure that all headers compile independently.
> FWIW, my former bash script used to report lots of non-compilable files
> inside boost.
> What do others think about this? I'd like to hear your comments on the
> approach and implementation, as well as bug reports ;-)
this is pretty cool!
I would suggest that for completeness there will be 'compile-header' rule that
works like like 'compile' but only taking header as input (and doing 'cast'
Otherwise, I don't see any reason why this should not be added to
Speaking about header names and escapes, unfortunately I don't see any good
solution. Header names clashes are possible, and we need to escape slashes
somehow. Maybe using dashes or underscores would be better, though.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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