Re: [Boost-build] --hash option undocumented?

Subject: Re: [Boost-build] --hash option undocumented?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-10-19 10:45:18

AMDG

On 10/19/2012 04:58 AM, John Maddock wrote:
> I've just had a very capricious issue with path names exceeding the
> system maximum which caused doxygen to produce truncated output (it
> didn't fail though, it actually looked like an xsltproc failure later). 
> Once I realized what the issue was I knew there was a bjam option to
> shorten the path names, but I haven't been able to find it in the docs,
> or in the output of bjam --help.  I had to search the mailing to
> eventually track it down :-(
> 
> So can we please:
> 
> 1) Document this somewhere.

It is mentioned, although in a somewhat obscure location:

http://www.boost.org/boost-build2/doc/html/bbv2/reference/buildprocess.html#bbv2.reference.buildprocess.targetpath

> 2) Add it to bjam's --help output.

I'm not sure that's a good idea.  The output of
bjam --help is specifically for building Boost.
This option shouldn't be needed for building Boost.
If it is, we need to shorten the file names.
However, this (and all the other options) should
show up in bjam --help-options which is very
sparse right now.

> 3) Is there any way that Boost.Build can detect over long paths up front
> and at least warn you about this issue?  It can take an awful long time
> to track down the cause if you're not expecting it.
> 

For doxygen, it isn't really possible, because
Boost.Build doesn't know about all the files
that doxygen creates.

In Christ,
Steven Watanabe