jimpark / unsis

Automatically exported from code.google.com/p/unsis
Other
59 stars 15 forks source link

cannot support long path over 260 characters #29

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 9 years ago
When a file's full path name is over 260 characters, NSIS will show "File: 
failed opening file..."

OS:Win7x64
NSIS:2.46.5 Unicode

PS:I use NSIS make up a eclipse RCP product, many files have a long file name 
such like 
"...\features\org.eclipse.mylyn_feature_3.6.5.v20120215-0100\META-INF\maven\org.
eclipse.mylyn.tasks\org.eclipse.mylyn_feature\pom.properties"

Original issue reported on code.google.com by Darknes...@gmail.com on 4 Feb 2013 at 6:40

GoogleCodeExporter commented 9 years ago

Original comment by j...@scratchpaper.com on 14 Mar 2013 at 8:53

GoogleCodeExporter commented 9 years ago
Is this problem happening while building your installer or when the installer 
is running?

Original comment by j...@scratchpaper.com on 14 Mar 2013 at 9:55

GoogleCodeExporter commented 9 years ago
For Unicode NSIS, did you try using "\\?\" prefix for all your paths? (This 
prefix does not work for ANSI NSIS.)

Original comment by j...@scratchpaper.com on 15 Mar 2013 at 1:42

GoogleCodeExporter commented 9 years ago
Thinks, that's OK.

Original comment by Darknes...@gmail.com on 25 Apr 2013 at 7:22

GoogleCodeExporter commented 9 years ago
Could you please put an example? I'm trying with 
File /r \\?\*.*

But I'm getting the error:
File: "\\?\*.*" -> no files found.

Original comment by gmazzo65 on 22 Jun 2013 at 6:53

GoogleCodeExporter commented 9 years ago
makensis.exe /DSETUP_FILES=\\?\D:\xxx\yyy\zzz\*.*

Original comment by Darknes...@gmail.com on 8 Aug 2013 at 1:55

GoogleCodeExporter commented 9 years ago
For such issues, you can use Long Path Tool, it works good.

Original comment by pawanyad...@gmail.com on 28 Jan 2014 at 11:38