Boost logo

Boost-Build :

Subject: Re: [Boost-build] [boost] path length too long for 64 bits builds
From: karzhenkov_at_[hidden]
Date: 2017-10-27 16:19:32


This issue is a symptom of poor bjam scalability.
I think, some changes are needed to solve the scalability problem.
Otherwise, we will have endless workarounds.

The “threadapi” feature illustrates the problem:

1. A feature added by some project leads to increasing the number of build
for every project it uses as dependency. Path length increases too (unless
the actual feature value
is its default value and the feature is not symmetric). Eventually it
reaches the system limit.
However, the dependency projects can not have any knowledge about this new
so we have many identical build variants placed in different folders.
Every new feature with two possible values increases number of such
duplicates twice.
We have the time and the disk space wasted.

2. For "threadapi" feature to work correctly (in particular, with
we were forced to make it global (i. e. “builtin”). This is far not perfect.
If we use such a workaround, is there some reason to have non-builtin


-----Исходное сообщение-----
From: Kuhl, Brian via Boost-build
Sent: Friday, October 27, 2017 6:31 PM
To: Boost.Build developer's and user's list
Cc: Kuhl, Brian
Subject: Re: [Boost-build] [boost] path length too long for 64 bits builds

I have the same issue with VxWorks cross-compile on Windows, I use the
b2 --abbreviate-paths
Which shortens the directory names enough that the tests complete.


> -----Original Message-----
> Gevorg Voskanyan via Boost-build
> Sent: Friday, October 27, 2017 3:10 AM
> To: boost_at_[hidden]; boost-build_at_[hidden]
> Cc: Gevorg Voskanyan
> Subject: Re: [Boost-build] [boost] path length too long for 64 bits builds
> On 27.10.2017 9:24, Vicente J. Botet Escriba via Boost wrote:
> > Hi,
> >
> >
> > we have an issue since we have added threadapi= .
> >
> >
> > On 64 bits windows machines we are seen
> >
> > Austin Beer said in
> >
> >
> > "FYI, the 64-bit Windows builds are failing due the unit tests
> > exceeding the 260 character filepath limit on Windows. Every filepath
> > includes
> > |\msvc-14.1\debug\address-model-64\threadapi-win32\threading-multi|.
> > Do you know if there is an easy way to shorten this? On the 32-bit
> > builds the filepaths don't have |\address-model-64| which is just
> > enough to keep them under the 260 character limit so they don't fail."
> >
> >
> > Is there a workaround to this issue without changing the specific part
> > of the test files folder structure?
> >
> >
> > Best,
> >
> > Vicente
> >
> >
Unsubscribe & other changes:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at