[1.33.0 RC1] libs/type_traits/docs/html needs boostbook.css
The html tables created by the Jamfile.v2 and type_traits.qbk in parent directory have no delimiters between columns and rows without a boostbook.css in the html directory. A copy of the boostbook.css from: libs/python/doc/tutorial/doc/html seems to work.
The html tables created by the Jamfile.v2 and type_traits.qbk in parent directory have no delimiters between columns and rows without a boostbook.css in the html directory. A copy of the boostbook.css from:
libs/python/doc/tutorial/doc/html
seems to work.
Where are you building the documentation from? The intent is that type traits along with all the other documentation gets built from boost-path/doc, in which case all the stylesheets are present (and a version of that documentation should ship in the zip). The Jamfile in libs/type_traits/doc is purely for testing/development purposes, which is why I didn't bother adding any stylesheets etc to cvs. John.
On 08/05/2005 04:55 AM, John Maddock wrote:
The html tables created by the Jamfile.v2 and type_traits.qbk in parent directory have no delimiters between columns and rows [snip] Where are you building the documentation from? The intent is that type
From $(BOOST_ROOT)/libs/type_traits/doc.
Where are you building the documentation from? The intent is that type
From $(BOOST_ROOT)/libs/type_traits/doc.
OK, I've just made two convenience changes: 1) The Jamfile copies the necessary graphics and css files into the local directory. 2) The Jamfile emits a warning message telling you not to build from that directory unless you just want to test the Type Traits doc build rather than update your installed docs. Regards, John.
On 08/05/2005 07:45 AM, John Maddock wrote:
Where are you building the documentation from? The intent is that type
From $(BOOST_ROOT)/libs/type_traits/doc.
OK, I've just made two convenience changes:
1) The Jamfile copies the necessary graphics and css files into the local directory. 2) The Jamfile emits a warning message telling you not to build from that directory unless you just want to test the Type Traits doc build rather than update your installed docs.
OK. Thanks John. Apparently I've misunderstood how bjam works. I somehow thought that, even when a Jamfile.v2 was invoked from a higher level directory, it behaved the same as when it was invoked from the Jamfile.v2 directory. I guess you expected $(BOOST_ROOT)/libs/type_traits/doc/Jamfile.v2 to be called from maybe $(BOOST_ROOT)/Jamfile.v2 and in that way, the boostbook.css file would be found. Hm..., but the index.html file created has: <link rel="stylesheet" href="boostbook.css" type="text/css"> so I'm still a little confused about how it can work since the above href seems to require that there be a boostbook.css in the same directory as the generated index.html file.
On 08/05/2005 08:07 AM, Larry Evans wrote: [snip]
file would be found. Hm..., but the index.html file created has:
<link rel="stylesheet" href="boostbook.css" type="text/css">
so I'm still a little confused about how it can work since the above href seems to require that there be a boostbook.css in the OK, I looked further and I guess you expected the docs to be created from $(BOOST_ROOT)/doc with that directory's Jamfile.v2. It makes sense now. Sorry for noise.
participants (2)
-
John Maddock -
Larry Evans