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.
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?
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
./b2 ... threadapi=pthread binary-format=elf abi=sysv
I'm open to any suggestion of a more elegant and extensible solution.
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?
On 03/16/2016 12:04 AM, Kuhl, Brian wrote:
> boost 1.59
> line 16
> ( this is the important one, though there are at least a dozen others in various other asio test files)
> line 47 and 65
> line 58 and 125
This one has been removed in develop.
> line 142 in default_threadapi
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk