<div class="gmail_extra">You should just get used to using shorter paths on the embarrassing OS.</div><div class="gmail_extra"><br></div><div class="gmail_extra">This is an early warning sign for you that your end users will also encounter these problems as they install your program on their systems in "non-short" root paths...<br>
<br></div><div class="gmail_extra">You can ignore it if you wish, but the fact remains that Windows STILL has many components in it that rely on full path names of ALL files being less than 260 characters.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">They do support longer file names, but there are still many legacy tools where the limit exists.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">
HTH,</div><div class="gmail_extra">David</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 23, 2012 at 8:26 AM, Andrea Crotti <span dir="ltr"><<a href="mailto:andrea.crotti.0@gmail.com" target="_blank">andrea.crotti.0@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
On 04/20/2012 12:36 PM, Eric Noulard wrote:<br>
<blockquote type="cite">
<pre></pre>
<pre>Nope, it would break backward compatibility, you can dig the ML
for discussion about that "issue".
My opinion is that building in-source is a bad habit that ought to be
discouraged but the fact is,
this is not currently easy to enforce out-of-source:
<a href="http://www.cmake.org/Bug/view.php?id=6672" target="_blank">http://www.cmake.org/Bug/view.php?id=6672</a>
</pre>
</blockquote>
<br>
<br></div>
Ok the make problem was my mistake sorry..<br>
<br>
we haven't really solved the long path problem yet unfortunately,
even building out of source we get some very long paths...<br>
<br>
Is there a way to shorten this generated path by CPack?<br>
<br>
C:/Temp/cmake_gen/_CPack_Packages/win32/NSIS<b><br>
</b><br>
Anyway the only solution I see for now is to check with a script the
length of the paths, and abort before trying to<br>
build anything.<br>
<br>
Or the other possible solution is to run cpack from an OS which is
not embarrassing, but not sure what version of CMake<br>
we have available and if the NSIS is working fine on that version..<br>
</div>
<br>--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br></div>