Re: [Boost-build] Manifest filename?

From: John Maddock (john_at_[hidden])
Date: 2007-09-23 13:32:08

Rene Rivera wrote:
>> It's the generator that needs to change since it's the one that
>> creates
>> all the internal targets. The attached version of boostbook.jam
>> implements the second option above. There might be a problem if you
>> set
>> your own <xsl:param>manifest property, so delete that before using
>> it.

Hmm, I'm still seeing lots of errors:

c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:971: in 
virtual-target.register-actual-name
warning: rulename $(cs1).main-target expands to empty string
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@357.actualize
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@366.actualize
c:/data/boost/boost/trunk/tools/build/v2\build-system.jam:488: in load
c:\data\boost\boost\trunk\tools\build\v2/kernel\modules.jam:261: in import
c:\data\boost\boost\trunk\tools\build\v2/kernel/bootstrap.jam:132: in 
boost-build
c:\data\boost\boost\sandbox\boost-build.jam:43: in module scope
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:972: in 
virtual-target.register-actual-name
warning: rulename $(cs2).main-target expands to empty string
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@357.actualize
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@366.actualize
c:/data/boost/boost/trunk/tools/build/v2\build-system.jam:488: in load
c:\data\boost\boost\trunk\tools\build\v2/kernel\modules.jam:261: in import
c:\data\boost\boost\trunk\tools\build\v2/kernel/bootstrap.jam:132: in 
boost-build
c:\data\boost\boost\sandbox\boost-build.jam:43: in module scope
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:992: in 
virtual-target.register-actual-name
warning: rulename $(cmt1).full-name expands to empty string
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@357.actualize
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@366.actualize
c:/data/boost/boost/trunk/tools/build/v2\build-system.jam:488: in load
c:\data\boost\boost\trunk\tools\build\v2/kernel\modules.jam:261: in import
c:\data\boost\boost\trunk\tools\build\v2/kernel/bootstrap.jam:132: in 
boost-build
c:\data\boost\boost\sandbox\boost-build.jam:43: in module scope
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:994: in 
virtual-target.register-actual-name
warning: rulename $(cmt2).full-name expands to empty string
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@357.actualize
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@366.actualize
c:/data/boost/boost/trunk/tools/build/v2\build-system.jam:488: in load
c:\data\boost\boost\trunk\tools\build\v2/kernel\modules.jam:261: in import
c:\data\boost\boost\trunk\tools\build\v2/kernel/bootstrap.jam:132: in 
boost-build
c:\data\boost\boost\sandbox\boost-build.jam:43: in module scope
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:996: in 
virtual-target.register-actual-name from module virtual-target
error: Duplicate name of actual target: 
<p..\bin.v2\doc\msvc-8.0\debug\threading-multi>catalog.xml
error: previous virtual target { 
boostbook%boostbook.generate-xml-catalog-catalog.xml.XML }
error: created from
error: another virtual target { 
boostbook%boostbook.generate-xml-catalog-catalog.xml.XML }
error: created from
error: added properties:  <xsl:param>root.filename=quaternion
error: removed properties:  <xsl:param>root.filename=sf_dist_and_tools
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:459: in 
actualize-no-scanner from module object(file-target)@357
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@357.actualize from module object(file-target)@357
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:463: in 
actualize-no-scanner from module object(file-target)@366
c:/data/boost/boost/trunk/tools/build/v2/build\virtual-target.jam:111: in 
object(file-target)@366.actualize from module object(file-target)@366
c:/data/boost/boost/trunk/tools/build/v2\build-system.jam:488: in load from 
module build-system
c:\data\boost\boost\trunk\tools\build\v2/kernel\modules.jam:261: in import 
from module modules
c:\data\boost\boost\trunk\tools\build\v2/kernel/bootstrap.jam:132: in 
boost-build from module
c:\data\boost\boost\sandbox\boost-build.jam:43: in module scope from module

However it does rename the manifest correctly when there is only one 
boostbook target, I'm attaching the Jamfile: can you see anything obviously 
wrong?

Many thanks, John.