Subject: Re: [Boost-build] Documentation build error on trunk
From: Daniel James (dnljms_at_[hidden])
Date: 2012-08-12 10:38:32
On 12 August 2012 14:53, Jurko GospodnetiÄ <jurko.gospodnetic_at_[hidden]> wrote:
>> Is this a new
> Not actually a new one, but a the message itself has been updated and the
> condition cleaned up a bit so it might catch more error cases than before.
> Before this check was only done when defining a project id using the
> 'use-project' rule, but not when doing it using the 'project' rule.
> All project id's live in a single namespace and I can not think of a
> reason why anyone would absolutely need to change one id to map to a
> different project than it already does. Any target references using that
> project id would then be in danger of being interpretted incorrectly.
> On the other hand, if you do see a reason why the old behaviour was
> 'desireable', I'll gladly update the code as needed.
Oh no, I was mainly just wondering if there might be similar problems
elsewhere, I'm pretty sure there are other poorly named projects
elsewhere. I fixed MPI on trunk, which fixed the documentation build.
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