Re: [Boost-build] Eliminating windows host pollution?

Subject: Re: [Boost-build] Eliminating windows host pollution?
From: Kuhl, Brian (brian.kuhl_at_[hidden])
Date: 2016-03-31 00:58:46

My workaround is failing on tests with longer names.
For example:
..\boost_1_59_0\bin.v2\libs\core\test\explicit_operator_bool_compile_fail_conv_int.test\gcc-vxworks\debug\binary-format-elf\link-static\target-os-vxworks\threadapi-pthread\explicit_operator_bool_compile_fail_conv_int.log 

fails to be created due to some windows pathname limit.

Is there any way to supply parameters to the build without increasing the directory depth?

Thanks

Brian Kuhl 

-----Original Message-----
From: Kuhl, Brian 
Sent: March-29-16 11:14 PM
To: 'steven_at_[hidden]'; Boost.Build developer's and user's list
Subject: RE: [Boost-build] Eliminating windows host pollution?

After a bit of fiddling I gave up trying to patch the jam files. 
Since most of these tests for OS.name="NT" result in setting a parameter default value; my current workaround is to override on commanline 
i.e.
./b2  ... threadapi=pthread binary-format=elf abi=sysv

I'm open to any suggestion of a more elegant and extensible solution.

Brian

-----Original Message-----
From: Boost-build [mailto:boost-build-bounces_at_[hidden]] On Behalf Of Steven Watanabe
Sent: March-16-16 9:32 AM
To: Boost.Build developer's and user's list
Subject: Re: [Boost-build] Eliminating widows host pollution?

AMDG

On 03/16/2016 12:04 AM, Kuhl, Brian wrote:
> 
> boost 1.59
> 
> libs/asio/test/Jamfile.v2
> line 16
> ( this is the important one, though there are at least a dozen others in various other asio test files)
> 
> libs/context/build/Jamfile.v2
> line 47 and 65
> 
> libs/iostreams/build/Jamfile.v2
> line 58 and 125
> 

This one has been removed in develop.

> libs/threads/build/Jamfile.v2
> line 142 in default_threadapi
> 

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build