<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 23, 2012 at 8:38 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 class="im">On 04/23/2012 01:32 PM, David Cole wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You should just get used to using shorter paths on the embarrassing OS.<br>
<br>
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>
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.<br>
<br>
They do support longer file names, but there are still many legacy tools where the limit exists.<br>
<br>
<br>
HTH,<br>
David<br>
<br>
</blockquote>
<br></div>
I agree with you, unfortunately I'm not the person that has to use smaller paths, just writing the build system..<br>
And good point about the installed application, I think I can assume however that if the CPack works also<br>
the installed application should work, because it doesn't have the ~20 chars needed for CPacking (but of course<br>
depends on where it will be installed).<br>
<br>
So well the only way is to make really sure there are no long paths around then :(<br>
</blockquote></div><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">If Windows is your target system, then yes: you must make sure all your paths are short enough.</div><div class="gmail_extra"><br></div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra">David</div><div class="gmail_extra"><br></div>