From: Jurko Gospodnetiæ (jurko.gospodnetic_at_[hidden])
Date: 2008-08-22 04:28:01
> On 22/08/2008, Jurko Gospodnetiæ <jurko.gospodnetic_at_[hidden]> wrote:
>> Well, if that is all you need, see if you can modify the relevant actions
>> to expand their variables using the :T variable expansion modifier. That
>> should simply cause all the back-slashes in the variable value to be
>> expanded as forward slashes. See the example above for an example.
> This needs to be configurable in user-config.jam - since the user
> might be using the cygwin doxygen or the windows doxygen. So would
> there be a preferred way pass this information in user-config.jam? The
> simplest thing to do would be to have two different tools (i.e. 'using
> doxygen' and 'using cygwin-doxygen'), probably with a common
> implementation. But some sort of parameter would probably be better.
I can add the option which would then be used something like:
using doxygen : <tool-type>cygwin ;
using doxygen : <tool-type>regular ;
with regular being the default.
This would change how the doxygen tools were used globally. If you
wanted to tweak this on a per-target level (and I do not see why would
would) I guess a separate <doxygen-tool-type> feature could be added or
something similar to that.
Any other suggestions for the interface? Note that I did not specify
a custom tool name in the declaration above (which would still come as
the first parameter).
I guess some sort of 'auto-detection' could be implemented as well if
someone could propose the algorithm for it, i.e. how would one go about
Could you please just try out tweaking the variable expansion in the
actions located in the tools/doxygen.jam module and post back the two
variants that work for:
- regular tools
- cygwin tools
My guess is that just the "$(<)" & $(>) expansions need to be changed
to $(<:T) & $(>:T) but unfortunately I have no way of testing this.
Also please test then with both native Windows and cygwin bjam build,
just to make sure we do not mess anything up.
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