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 06:03:24

On Wednesday 24 June 2009 Martin Dyring-Andersen wrote:

> Hello everybody,
> 
> I have a Boost.Build based project which is currently being built in Windows, Darwin, Linux (Debian) and FreeBSD. Everything builds smoothly with the exception of some tests..
> 
> Given the following directory structure as an example:
> 
> $HOME/Projects/TFS/MyProject Name Containing Spaces/jamroot
> $HOME/Projects/TFS/MyProject Project Name Containing Spaces/somedynamiclib/jamfile
> $HOME/Projects/TFS/MyProject Project Name Containing Spaces/test/jamfile
> 
> the test/jamfile contains (simplified):
> 
> test-suite test
> 	:	[ run test.cpp /somedynamiclib : : : : ]
> ;
> 
> So, during build I should get a test executable that is capable of loading "somedynamiclib". The result is this on the different platforms:
> 
> * Windows works like a charm
> 
> * Darwin fails with this error:
> /bin/sh: line 1: MyProject: command not found
> /bin/sh: line 4:  5573 Trace/BPT trap
> 
> * Debian works, but gives the following warning:
> /bin/sh: line 1: MyProject: command not found
> /bin/sh: line 2: export: `LD_LIBRARY_PATH': not a valid identifier

Can you update Boost.Build from SVN and try again? I've just fixed this. If you
were using some system version of Boost.Jam, you'd also need to build Boost.Jam
from SVN. If you were using 1.39 version of Boost.Jam, it's good enough.

> As a side note: any progress / plans for a release capable of hashed build directories? 
> I have run into the path length issue on Windows a number of times, for now I have 
> avoided them by using --abbreviate-paths but it feels like postponing the inevitable. ;-)

There are no concrete plans at present. If you, or somebody else, find me a suitably
licensed SH1 or MD5 implementation, it would be a big help :-)

- Volodya