Re: [Boost-build] Manifest filename?

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-09-23 13:09:44

John Maddock wrote:
> Rene Rivera wrote:
>> John Maddock wrote:
>>> Is it possible to specify a name for the manifest file created by
>>> Boostbook in BBv2?
>> Yes, add an <xsl:param>manifest=my.manifest to the target. But, that
>> will cause the docs to be rebuilt all the time since the BBv2 code
>> looks for the HTML.manifest as the real target. Hence if it never
>> exists, in the name BBv2 is looking for, it will always think the
>> docs are not built.
> 
> Ah, I hadn't spotted that, but I still get bjam errors if there are two 
> boostbook targets in one file even after setting <xsl:param>manifest:

Yep... I guess my post implied that it would make BBv2 work. Sorry, I 
didn't mean to imply that :-(

>>> I want to have two Boostbook targets in the same Jamfile: generating
>>> different html/pdf files (but in the same directory tree), but am
>>> currently prevented from that because the two targets both want to
>>> create the same manifest file "HTML.manifest".  Alternatively can
>>> the manifest filename be changed to "mydocname.HTML.manifest" ?
>> Before I look more than I have into doing something... What would you
>> expect to happen with the other equally named files, in particular
>> index.html?
> 
> Well I'm using <xsl:param>root.filename to change that, as far as I can see 
> that name isn't hard coded in bbv2, or is it?

It's not.

> As for the manifest name, if it could be changed to match the value of 
> <xsl:param>manifest that would be truely magnificent: provided it solves the 
> "two targets in one file" issue :-)
> 
> Otherwise we could use the name of the boostbook target for the manifest 
> name and ignore <xsl:param>manifest I guess.  BTW: I tried changing the bbv2 
> code to look for $(name).HTML.manifest in "rule run ( project name ? : 
> property-set : sources * : multiple ? )" inside boostbook.jam, but that just 
> led to some inscutable errors I couldn't fix :-(
> 
> Any ideas?

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.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo