From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-08-21 14:28:36
> At the moment, if you call cygwin doxygen or xsltproc from boost build
> on the windows command line, they don't work because they require
> cygwin paths (forwards slashes). Would it be possible to configure
> boost build to use forward slashes for certain tools, but still use
> back slashes for others?
The change you require would actually entail more than changing
forward slashes would it not? Absolute paths would need to be changed to
something like /cygdrive/c/xxx/yyy/zzz with possibly some more escapes
being added for spaces, special characters, etc.
Anyone got some working code implementing this transformation?
Also, how should Boost Build/Jam know whether to apply the
transformation to a specific path?
This can not be specified simply for 'all paths in an action' as
Boost Jam has now way of telling what part of an action is a 'path'.
We already have a :W variable modifier in Boost Jam which does this
conversion for a specific variable content but this works only for a
cygwin built Boost Jam as it uses cygwin's
I guess one alternative would be to add a new variable modifier to
Boost Jam which would always convert a path from Win32 format to Cygwin
without relying on Cygwin's APIs. And if we could do that then would
there be any point in keeping the old :W modifier around? Or should
perhaps that one be changed to work without cygwin as well?
Another alternative is to have a rule (whether written using Jam or
as a builtin rule - does not really matter) which implements this
transformation and then call that when needed. Although I do not think
we could use that for transforming paths passed as parameters to actions
so I guess that does not help us much.
Hmmm, now that I think of it I remember seeing something like this in
the python.jam module... but do not have the time to check right now...
Anyone else got any more thoughts on this?
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