Re: [boost] [test] trunk breakage

Subject: Re: [boost] [test] trunk breakage
From: Robert Ramey (ramey_at_[hidden])
Date: 2010-01-07 12:06:48

Actually what I would like to do is the following:

a) do an SVN update of my BoostRelease directory. This is what
I do now.  Works great. So I have on my machine the whole
"next release"

b) Then I want to be able to invoke something like
bjam " build documentation" from the BoostRelease directory.
I think I can do this and in fact I think I have done this -
I just forgot the procedure.

This would give me the following:

a) The documentation on my local system for the
"next release"

b) the build process should much simpler and more
up to date then downloading a whole new zip.  The
build would only have to build those components which
have changed.

c) I could choose which kind of documentation I wanted
html or pdf or (maybe someday) windows help file

Robert Ramey

Daniel James wrote:
> 2010/1/7 Robert Ramey <ramey_at_[hidden]>:
>>
>>> What I really need is to be able to
>>> build it (the documentation) locally from the release branch.
>
> I build the documentation about once a week, more often when
> releasing. The html files in subversion redirect to the trunk
> documentation on the web, which is normally pretty good. If you want
> the release branch documentation you can get it from:
>
> http://boost.cowic.de/rc/boost-docs.7z
>
> It only contains the doc/html directory so it needs to extracted in
> place in order to use the images and stylesheets. Something like this
> should do the trick:
>
> 7za -o$BOOST_ROOT/doc -y x boost-docs.7z
>
> You need to install 7-zip. The command line version is usually called
> something like p7zip.
>
> Daniel
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost