|
Boost-Build : |
Subject: Re: [Boost-build] [boost] path length too long for 64 bits builds
From: Kuhl, Brian (brian.kuhl_at_[hidden])
Date: 2017-10-27 13:31:55
Vicente,
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.
Brian
> -----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
> > https://github.com/boostorg/thread/pull/188#issuecomment-339829423
> >
> > "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
> >
> >
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