From: Jurko Gospodnetiæ (jurko.gospodnetic_at_[hidden])
Date: 2008-02-15 04:43:04
> Reviews of the proposed changes are welcome. I'd like to commit a
> (surely improved) version to trunk after 1.36 is out.
> Comments ?
Sorry, I did not test this or take a look at the implementation but
still wanted to ask the question...
If this problem with multiple files in different folders using the
same file names gets 'fixed'. Then how will we tell Boost Build to build
just one of them from the command-line?
Currently you can just say 'bjam <final-target-file-name>' and it
builds that target file even when there is no explicitly defined top
level target by the given name. Example: 'bjam a.obj' builds a.cpp...
This is very useful e.g. when tweaking header files while tracking
down compiler warnings and you do not want each such tweak to cause all
your modules to be recompiled that way it takes a looooong time for the
build to get to the failing module. (We were doing this just
yesterday... :-) )
If you simply add a prefix/suffix to the generated file name then it
needs to be intuitive enough for the user to know when to use it on the
command line... Maybe this is not be too much trouble since he can first
see the actual target file name by building the sources... but maybe it
would - can not decide without actually playing with a prototype solution...
Perhaps a good solution would be to generate folders in the final
build tree that represent the source tree and then the user would need
to specify the full path to the built target file. If this is done then
I guess one would have to be careful about how such a tree is built when
using generators generating targets from multiple sources... and when
sources are spread over far far far away folders....
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