Ticket #3273 (closed: fixed)
64-bit Windows Vates installer does not set correct install prefix
| Reported by: | Martyn Gigg | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 30 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Martyn Gigg |
Description
The Vates intaller for version 1.29.12884 does not set the correct default prefix on the installation directory.
Running the installer, clicking next then I agree allows the user to pick the install location. The default comes up as "\Mantid_Vates 1.29.12884" and is invalid as it as no prefix.
This does not occur on the 32-bit version and as just tested it is fine from a development version from 26/06/2011
Change History
comment:2 Changed 9 years ago by Owen Arnold
Diffing project.nsi files generated on my local machine and on the build server. Notice that $PROGRAMFILES is not used to construct the $INSTALLDIR on the build server cmake/cpack generated project.nsi, but it is on my local machine.
Environments nearly identical other than that the build server is a VM.
Could it be that CPack is not doing the generation properly on a VM?
comment:3 Changed 9 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
Fixed after speaking to Kitware developers. Problem with CMake 2.8.3. Upgrading to 2.4.5 fixed the issue.
comment:4 Changed 9 years ago by Martyn Gigg
- Status changed from verify to verifying
- Tester set to Martyn Gigg
Looks like this is an issue specific to the 64bit build server instance we have here. Packaging on my 64bit development machine correctly sets the first part of the destination directory. May still be able to fix.