Re: [Boost-build] test-suite / run problem with paths containing spaces

Subject: Re: [Boost-build] test-suite / run problem with paths containing spaces
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-06-24 11:37:33

On Wednesday 24 June 2009 Martin Dyring-Andersen wrote:

Hi Martin,

> 
> Thanks a lot - now tests run perfectly on all platforms!

Great.

> 
> > > Actually I was going to suggest either using the Boost CRC library (since I
> > don't think it is
> > > actually necessary with a crypto-safe hash anyway?)
> > 
> > Well, Boost CRC is probably not strong enough for this purpose :-)
> 
> Just trying to keep it simple. :-)
> 
> I googled a bit for CRC collision rates. This page seems interesting and concludes that chances of a CRC64 collision is extremely low (at least for that class of input data):
> http://apollo.backplane.com/matt/crc64.html
> 
> So maybe it is not such a bad idea after all. 

Well, another problem is that using Boost library is too heavy a dependency :-)

> As for a free md5 implementation, IANAL, but this puppy seems to fit licensing wise:
> http://sourceforge.net/project/showfiles.php?group_id=42360

Looks good -- I did not run into this implementation before. Since we're gonna
need MD5 in Boost.Jam anyway, I've integrated this code. If you grab Boost.Jam
from SVN, and also apply the attached Boost.Build patch, all the target paths will
start using MD5 hashes. I did not commit Boost.Build part, because it needs
some work -- in particular a way to explicitly request MD5 paths from command
line, and some mechanism to report which properties a given MD5 path correspond
to -- but the patch I've posted should be enough for experimentation.

> > > or, alternatively, use the Windows
> > > Wide/Unicode filesystem functions to support the long paths.
> > 
> > Is there some alternative API that does not have path length limits?
> 
> There is a limit, but it is high enough that it should be sufficient: 
> 32,767 characters according to http://msdn.microsoft.com/en-us/library/aa363858(VS.85).aspx

Thanks. I'll keep this in mind.
 
- Volodya