Boost logo

Boost-Build :

From: Ilya Sokolov (fal_delivery_at_[hidden])
Date: 2007-11-21 03:40:40

Edward Diener wrote:

> [snip]

> There is no other output to stderr or stdout. It does look as if the
> xsltproc command is trying to write output to "html/" but my
> understanding is that the -o option is supposed to be a file

You are wrong

> but the
> option in the command line above points to a directory. Is that what is
> perhaps causing the problem ? Of course somewhere in the bowels of Boost
> Build the xsltproc command line is being generated so I have no idea why
> the -o option points to a directory rather than a file. There is nothing
> being output in the "html/" relative directory on my machine after
> xsltproc is run.
> What is most annoying about Boost Build is that one gets back no idea
> why something is said to have failed. I find this a real weakness of
> Boost Build from the end user's perspective.

In this case it is not a weakness of Boost Build, it is a bug in
xsltproc (and in your batch file, see below). We are off topic now.

>> BTW, error code may be less than zero on windows
> That may be possible but I have no idea how to check if the errorlevel
> is less than zero in a cmd batch file.

if %errorlevel% lss 0 (
   rem errorlevel is less than zero
if %errorlevel% neq 0 (
   rem errorlevel is not equal to zero
if errorlevel 1 (
   rem warning: errorlevel is equal to or greater than 1
if not errorlevel 1 (
   rem warning: errorlevel is less than 1, i.e. 0 or negative!

Now I believe that running xsltproc from the command line does not succeeds.

> [snip]

>>>> 2. try another xsltproc (e.g.
>>> I will give it a try, but this business of trying to setup and use the
>>> Boost documentation system, according to instructions, and failing to be
>>> able to do so, is getting old. I think Boost should either consider
>>> something better than this mess or get it working someday in this century.
>>> I did get the xsltproc directly from the link in the The BoostBook
>>> Documentation Format, and that link is at
>>> Is that
>>> link's implementation of xsltproc broken perhaps ?
>> AFAICT, its purpose is to contain this old fix:
> 'its' meaning the metacomm link ?



Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at