Hi Mike,

Thanks, I didn’t know that. Well... gonna have to take the plunge some day, 
might aswell be now... :)

Regards
/R

From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of mike lojkovic
Sent: den 8 september 2016 15:58
To: Cmake@cmake.org
Subject: Re: [CMake] Windows path too long


Can you change to windows 10? If you are on 10, you can turn the restriction 
off. Otherwise, I believe there's complicated ways to shorten the path.

http://m.slashdot.org/story/311861

On Sep 7, 2016 8:07 AM, "David Cole via CMake" 
<cmake@cmake.org<mailto:cmake@cmake.org>> wrote:
I suppose the obvious "use shorter paths and names" is not possible or hard to 
enforce?


David


> On Sep 7, 2016, at 2:55 AM, Robert Bielik 
> <robert.bie...@dirac.com<mailto:robert.bie...@dirac.com>> wrote:
>
> I have a problem with a VS 2015 project, where the build state path becomes 
> too long:
>
> Severity    Code    Description    Project    File    Line    Suppression 
> State
> Error    MSB3491    Could not write lines to file 
> "processor_withAVeryVeryLongName.dir\Release\processo.92BD73FC.tlog\processor_withAVeryVeryLongName.lastbuildstate".
>  The specified path, file name, or both are too long. The fully qualified 
> file name must be less than 260 characters, and the directory name must be 
> less than 248 characters.    processor_withAVeryVeryLongName    C:\Program 
> Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets    312
>
> The line in Microsoft.CppBuild.targets is:
>
> <WriteLinesToFile Overwrite="true" File="$(LastBuildState)" 
> Lines="$(ProjectStateLine);$(ProjectEvaluationFingerprint)"/>
>
> I've set CMAKE_OBJECT_PATH_MAX to 240, but I don't think it will affect 
> this...
>
> Ideas ?
>
> This is with CMake 3.5.2.
>
> Regards
> /Robert
>
> --
>
> Powered by www.kitware.com<http://www.kitware.com>
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake

--

Powered by www.kitware.com<http://www.kitware.com>

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to