Re: [Boost-build] Documentation build error on trunk

Subject: Re: [Boost-build] Documentation build error on trunk
From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2012-08-12 09:53:13

   Hi.

>> Sure, I'll be available tomorrow. I'll also run a full documentation
>> build now to check that your boostbook changes are okay.
>
> It failed because of a duplicate project. I'll fix it now. Is this a new check?
>
> error: at /Users/daniel/boost/release/build/build-trunk/boost/libs/mpi/doc/Jamfile.v2:5
> error: Attempt to redeclare already registered project id '/boost/mpi'.
> error: Original project:
> error:     Name:
> Jamfile</Users/daniel/boost/release/build/build-trunk/boost/libs/mpi/build>
> error:     Main id: ---
> error:     File: ../libs/mpi/build/Jamfile.v2
> error:     Location: ../libs/mpi/build
> error: New project:
> error:     File:
> /Users/daniel/boost/release/build/build-trunk/boost/libs/mpi/doc/Jamfile.v2
> error:     Location:
> /Users/daniel/boost/release/build/build-trunk/boost/libs/mpi/doc

   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.

   Hope this helps.

   Best regards,
     Jurko Gospodnetić