Re: [Boost-build] [boostbook] Building Boost documentation

From: Edward Diener (eldiener_at_[hidden])
Date: 2007-11-21 17:54:19

Ilya Sokolov wrote:
> 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

Then the documentation for xsltproc is wrong, which is not surprising to me.

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

You are correct. The errorlevel returned is -1073741819.