MantisBT - CMake
- Unzip the attached Test.zip file;
- Either:
- Double click on the packageproj.bat file; or
- Open a command prompt window, cd to the directory where you unzipped the file, and execute the packageproj.bat file from the command prompt;
- Execute [Test]\build\Test-0.1.1-win32.exe and/or unzip the [Test]\build\Test-0.1.1-win32.zip file;
- Go to the installation/unzipped folder and check the permissions for our deployed readOnlyFile.txt file.
Expected result: our deployed readOnlyFile.txt file should be readable only.
Actual result: our deployed readOnlyFile.txt file is read-writable.
Otherwise, it might be worth pointing out that, on Windows and for NSIS and ZIP respectively, [Test]\build\_CPack_Packages\win32\NSIS\Test-0.1.1-win32\readOnlyFile.txt and [Test]\build\_CPack_Packages\win32\ZIP\Test-0.1.1-win32\readOnlyFile.txt are read-only. So, could it be that the problem is during the packaging itself? It certainly looks like it.
From a reply I got on the mailing list, it would seem that the same libarchive is used for ZIP on the different platforms (see http://www.cmake.org/pipermail/cmake/2011-April/044124.html [^]). Still, I get the feeling that the problem might still be there (as we know, permissions are handled in a very different way on Windows compared to Linux / Mac OS X, so...?).
Finally, regarding NSIS, having checked the contents of [Test]\build\_CPack_Packages\win32\NSIS\project.nsi, it seems to me that the NSIS project file misses a call to SetFileAttributes with READONLY as a parameter. This would ensure that once deployed, our readOnlyFile.txt is indeed read-only. At least, this is what I had to do for another project of mine for which I had to 'manually' write a NSIS project file.
| related to | 0012865 | closed | Kitware Robot | CPack generated archives don't have correct permissions when cross compiling on windows |
Test.zip (1,558) 2011-04-30 13:52https://public.kitware.com/Bug/file/3841/Test.zip