Re: [Boost-docs] Can't build bjam docs

Subject: Re: [Boost-docs] Can't build bjam docs
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-09-19 18:22:51

John Maddock wrote:
> John Maddock wrote:
>>>> PS. I guess I continue trying to /kludge/ it into a working state.
>>>> As I really need to do a bjam release this weekend.
>>> Please find attached a Jamfile that works for me, and looks for
>>> images and logo's in the existing locations (as long as the docs are
>>> in a directory called "doc").  I'll look into fixing the XSL so it
>>> emulates the old behaviour as well.
>>>
>>> Hope this gets you going in the mean time, John.
> 
> On second thoughts.... do you need to ship *just* the contents of the 
> tools/jam/doc/html directory?  If so the previous Jamfile won't do it, but 
> will work if you're shipping all of tools/jam/.

Something like that... I copy the contents of the html dir into the src 
dir and packages the files in the src dir. So yes I need to move them, 
and hence really need relative paths.

> The Jamfile-hack workaround would be to revert to using boost.root=. and 
> simply install the images in a different directory: html/doc/html/images 
> rather than the usual html/images.

Sounds twisted ;-) But I might be able to do something like that, as 
long as the html files themselves can go into the src (i.e. html) dir. 
But in general this behavior makes it really inconvenient for people to 
use BoostBook, and hence Quickbook, outside of Boost.

> I've played around trying to fix things in the XSL so that we preserve the 
> old behaviour as well as providing the option to set boost.root and have 
> everything "just found", but there's no easy way, the best I can come up 
> with is to replace:

[... I get confused by xsl, but I can almost follow that]

> Basically the idea is that if boost.root is set to within the current 
> directory tree (or is not set and is taking it's default value), then we go 
> back to the old default of images/ for the images path.  This isn't quite 
> compatible with the intended new style behaviour if you use either ".." or 
> "." as the boost.root.  On the other hand, it is reasonably sensible, if a 
> potential for causing surprises.

Ah, OK.

> Let me know if you want me to commit the change.

I have a simple question... Why is the change from the previous behavior 
needed?

> The other thing I'd still really like to see fixed, is bjam's insistance on 
> stripping trailing /'s from paths.  Currently it breaks all kinds of 
> Boostbook XSL options :-(  Do you know if there is any way to work around 
> this?

I'm looking at it now... Since I didn't know the problem existed until I 
ran into it last night :-)

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