|
Boost-Build : |
From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-07-01 03:25:17
Hi.
>> Yes, that seems to be the problem, which would seem to implicate
>> Boost.Build (?) for failing to recognize that these two targets are
>> really the same. Any help from the Boost.Build gurus?
>
> If there is a problem - I do not see it. What exact Boost Build
> version are you using and what tree are you trying to build?
>
> I just tried it with the trun Boost Build and with the current Boost
> trunk on Windows and Boost Build has no problems with this. It failed to
> build the documentation but that is most likely due to mu doxygen
> toolchain not being set up correctly.
Forgot to mention in my previous post I tried it on Windows XP, not
Ubuntu.
Also, I just tried it some more this morning including trying to fool
around with the BuildDir options but all paths kepts getting detected
consistently.
I did find a bug in doxygen.jam in case you specify an absolute build
dir and posted a patch for it but that does not seem to be related to
your problem.
Changeset link: http://svn.boost.org/trac/boost/changeset/46940
I also found a potential bug with some doxygen.xml.path xslt
parameter construction which was getting constructed using internal
Boost Build path format and not the native OS path format and was not
getting quoted so would not work correctly in case the path contained
spaces. The same patch adds several more quotes to the quickbook.jam &
doxygen.jam modules to give them more chance to work correctly with
paths containing spaces.
Changeset link: http://svn.boost.org/trac/boost/changeset/46942
Hope this helps.
Best regards,
Jurko GospodnetiÄ
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