From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-07-12 10:13:24
> I have added response file support to the toolset :). I have also added the
> "-cwd include" flag to the compilation phase to search the directory of the
> included file first for #include files.
> The actions may need to be fixed because of wrapping caused via e-mail :(.
I've comitted the toolset. Thanks!
Please update and make sure it still work ;-)
> It still does not correctly handle command/compiler (i.e. duplicating the
> compiler name) because I am unsure how you intend on using command to
> specify the location of the linker, etc. without duplicating the full path
> for each and how to resolve the paths if using a tool within a different
> directory (e.g. windres for the msvc toolset). This is not a big issue at
> the moment since the other tools share this defect and when it is fixed it
> can be done toolset wide once a fix has been made.
Yes, that's reasonable.
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