Manifest filename?

Is it possible to specify a name for the manifest file
created by Boostbook 
in BBv2?

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" ?

Thanks, John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

John Maddock wrote:

> Is it possible to specify a name for the manifest file
created by
> Boostbook in BBv2?
> 
> 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" ?

>From my point of view, this is more boost-docs questions
than a boost-build
one -- he manifest file is created by XSLT, and I don't know
where, or how.
Boost.Build will need adjustment if XSLT starts to produce
differently
named manifest, but XSLT change should be done first.

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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.

> 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?


-- 
-- 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
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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.

You can also prevent the manifest from getting generated
with 
<xsl:param>generate.manifest=0, but obviously with the
same rebuild issue.


-- 
-- 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

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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:

c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:996: in 
virtual-target.register-actual-name from module
virtual-target
error: Duplicate name of actual target:
<phtml>HTML.manifest
error: previous virtual target { 
boostbook%boostbook.docbook-to-htmldir-HTML.manifest.HTMLDIR
{ 
boostbook%boostbook.boostbook-to-docbook-math.docbook.DOCBOO
K {
quickbook%quickbook.quickbook-to-boostbook-math.xml.XML { 
math.qbk.QUICKBOOK } }
 } }
error: created from ./standalone
error: another virtual target { 
boostbook%boostbook.docbook-to-htmldir-HTML.manifest.HTMLDIR
{ 
boostbook%boostbook.boostbook-to-docbook-quaternion.docbook.
DOCBO
OK {
quickbook%quickbook.quickbook-to-boostbook-quaternion.xml.XM
L { 
quaternion.qbk.QUICKBOOK } } } }
error: created from ./quat_standalone
error: added properties: 
<xsl:param>manifest=quaternion.manifest 
<xsl:param>root.filename=quaternion
error: removed properties: 
<xsl:param>root.filename=sf_dist_and_tools
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:459: in 
actualize-no-scanner from module object(file-target)362
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)362.actualize from module
object(file-target)362
c:/data/boost/boost/trunk/tools/build/v2build-system.jam:48
8: in load from 
module build-system

etc.

>> 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?

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?

Many thanks, John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

John Maddock wrote:
> 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?

Just a quick update: dependency checking still seems to work
if 
<xsl:param>root.filename is set, it's just the
manifest name that's messing 
things up as far as I can see at present.

John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

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/buildvirtual-targe
t.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/buildvirtual-targe
t.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)357.actualize
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)366.actualize
c:/data/boost/boost/trunk/tools/build/v2build-system.jam:48
8: in load
c:databoostboosttrunktoolsbuildv2/kernelmodules.jam:
261: in import
c:databoostboosttrunktoolsbuildv2/kernel/bootstrap.ja
m:132: in 
boost-build
c:databoostboostsandboxboost-build.jam:43: in module
scope
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.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/buildvirtual-targe
t.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)357.actualize
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)366.actualize
c:/data/boost/boost/trunk/tools/build/v2build-system.jam:48
8: in load
c:databoostboosttrunktoolsbuildv2/kernelmodules.jam:
261: in import
c:databoostboosttrunktoolsbuildv2/kernel/bootstrap.ja
m:132: in 
boost-build
c:databoostboostsandboxboost-build.jam:43: in module
scope
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.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/buildvirtual-targe
t.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)357.actualize
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)366.actualize
c:/data/boost/boost/trunk/tools/build/v2build-system.jam:48
8: in load
c:databoostboosttrunktoolsbuildv2/kernelmodules.jam:
261: in import
c:databoostboosttrunktoolsbuildv2/kernel/bootstrap.ja
m:132: in 
boost-build
c:databoostboostsandboxboost-build.jam:43: in module
scope
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.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/buildvirtual-targe
t.jam:459: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)357.actualize
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:463: in 
actualize-no-scanner
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)366.actualize
c:/data/boost/boost/trunk/tools/build/v2build-system.jam:48
8: in load
c:databoostboosttrunktoolsbuildv2/kernelmodules.jam:
261: in import
c:databoostboosttrunktoolsbuildv2/kernel/bootstrap.ja
m:132: in 
boost-build
c:databoostboostsandboxboost-build.jam:43: in module
scope
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:996: in 
virtual-target.register-actual-name from module
virtual-target
error: Duplicate name of actual target: 
<p..bin.v2docmsvc-8.0debugthreading-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/buildvirtual-targe
t.jam:459: in 
actualize-no-scanner from module object(file-target)357
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)357.actualize from module
object(file-target)357
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:463: in 
actualize-no-scanner from module object(file-target)366
c:/data/boost/boost/trunk/tools/build/v2/buildvirtual-targe
t.jam:111: in 
object(file-target)366.actualize from module
object(file-target)366
c:/data/boost/boost/trunk/tools/build/v2build-system.jam:48
8: in load from 
module build-system
c:databoostboosttrunktoolsbuildv2/kernelmodules.jam:
261: in import 
from module modules
c:databoostboosttrunktoolsbuildv2/kernel/bootstrap.ja
m:132: in 
boost-build from module
c:databoostboostsandboxboost-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.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build