Well, this seems to work around it, but there must be another way.
in my Jamroot I added
local attr = [ project.attributes project-config ] ;
module $(attr)
{
self.location = [ modules.peek project : .global-build-dir ] ;
}
On Mon, Apr 19, 2010 at 5:16 PM, Jonathan Brannan
I'm trying to make some documentation for a project that uses boost.build v2. I'm getting the error: Generating Output File: ../build/docs/gcc-4.3/docs/my_doc.xml
file /tmp/jam23e7c859.000 <?xml version="1.0"?> <!DOCTYPE catalog PUBLIC "-//OASIS/DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
http://www.boost.org/tools/boostbook/dtd/" rewritePrefix="file:///home/build/boost_1_39_0/tools/boostbook/dtd/"/ </catalog>
text-action /bin/boostbook_catalog.xml
cat "/tmp/jam23e7c859.000" > "/bin/boostbook_catalog.xml"
/bin/sh: line 1: /bin/boostbook_catalog.xml: Permission denied
I have: docs/Jamfile using xsltproc ; using boostbook ; using fop : /usr/bin/fop : : /usr/bin/java ; using quickbook : /home/build/boost_1_39_0/dist/bin/quickbook ;
xml my_doc : my_doc.qbk ;
boostbook standalone : my_doc :
I narrowed the problem down to having a ../project-config.jam. This is being detected as the root-project in rule xml-catalog ( ) in tools/boostbook.jam. If I remove the project-config.jam, it correctly detects the build path and goes correctly. Is my use wrong or is there something else I can do to work around this? I tried adding a project in the docs jamfile, but it did not seem to help.