Hi - I've run into an issue using Inno Setup Unpacker to extract the contents of some installers we create in-house.
Due to some comically-long paths the development team has added to our software we use the windows extended path format for our destination directories, like so:
This works properly for the actual installer, but innounp ends up putting all of the files in an _ /{app} directory at the root of the current drive, ala C:_{app}. Only the 'Additional Files' innosetup files end up in the directory specified with -d.
Is there anything I can do to override this behavior? The -e does properly dump all files into the specified directory, but unfortunately that's not suitable for what we're trying to do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Certainly - the attached zip contains an installer, the .iss files used to create it, and text files with the build command and the extraction results, showing the contents of the intended target directory and the _ folder at the root level where the files ended up.
This stackoverflow page illustrates the problem that switching to the extended path syntax solved for us: https://stackoverflow.com/questions/38789616/inno-setup-compiler-cannot-find-the-path-specified-error-with-long-paths
(Note that the included paths in this case are actually quite short - I deliberately trimmed the file down to a short example to remove actual long path names from the equation.)
Hi - I've run into an issue using Inno Setup Unpacker to extract the contents of some installers we create in-house.
Due to some comically-long paths the development team has added to our software we use the windows extended path format for our destination directories, like so:
This works properly for the actual installer, but innounp ends up putting all of the files in an _ /{app} directory at the root of the current drive, ala C:_{app}. Only the 'Additional Files' innosetup files end up in the directory specified with -d.
Is there anything I can do to override this behavior? The -e does properly dump all files into the specified directory, but unfortunately that's not suitable for what we're trying to do.
Could you provide a sample installer for tests? It would be simpler when there are some files with reproducable behavior to play with.
Certainly - the attached zip contains an installer, the .iss files used to create it, and text files with the build command and the extraction results, showing the contents of the intended target directory and the _ folder at the root level where the files ended up.
This stackoverflow page illustrates the problem that switching to the extended path syntax solved for us: https://stackoverflow.com/questions/38789616/inno-setup-compiler-cannot-find-the-path-specified-error-with-long-paths
(Note that the included paths in this case are actually quite short - I deliberately trimmed the file down to a short example to remove actual long path names from the equation.)