MantisBT - CMake |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0015635 | CMake | (No Category) | public | 2015-06-29 09:18 | 2016-06-10 14:31 |
|
Reporter | kdawgud | |
Assigned To | Kitware Robot | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | moved | |
Platform | X86-64 | OS | Windows 7 64-bit | OS Version | SP1 |
Product Version | CMake 3.1 | |
Target Version | | Fixed in Version | | |
|
Summary | 0015635: CPACK_NSIS_MODIFY_PATH has no affect on PATH variable |
Description | I have a 64-bit windows C++ project where I'm using the NSIS generator for CPack. The installer appears to work fine, except that the PATH variable is not changed at all even when specified by the user during install. The CPACK_NSIS_MODIFY_PATH variable is specified in the cpack config to support changing the path during install. It doesn't seem to matter if "all users" or "current user" is selected. |
Steps To Reproduce | 1) Use CMake 3.1 to generate MS Visual Studio solution file for 64-bit (VS 2010).
2) Build project, then build "package" withing visual studio
3) Run the NSIS .exe installer generated by cpack
4) Select "Add xxxx to the system PATH for all users" when prompted
5) When NSIS install is complete, observe that "echo %PATH%" does not reflect the installed path
6) Reboot and still observe 0000005 holds true. |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | 0014716 | closed | Brad King | CMake installer can't modify %PATH% if it's 'loo long'. | related to | 0010257 | closed | Bill Hoffman | Installer erasing windows PATH |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2015-06-29 09:18 | kdawgud | New Issue | |
2015-06-29 13:19 | David Cole | Note Added: 0039000 | |
2015-06-29 13:19 | David Cole | Relationship added | related to 0014716 |
2015-06-29 13:19 | David Cole | Relationship added | related to 0010257 |
2015-06-29 13:23 | kdawgud | Note Added: 0039001 | |
2015-06-29 13:25 | kdawgud | Note Edited: 0039001 | bug_revision_view_page.php?bugnote_id=39001#r1812 |
2016-06-10 14:29 | Kitware Robot | Note Added: 0042802 | |
2016-06-10 14:29 | Kitware Robot | Status | new => resolved |
2016-06-10 14:29 | Kitware Robot | Resolution | open => moved |
2016-06-10 14:29 | Kitware Robot | Assigned To | => Kitware Robot |
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Notes |
|
(0039000)
|
David Cole
|
2015-06-29 13:19
|
|
How long is your PATH before you run the installer?
Is it perhaps related to one of these bugs, talking about "PATH too long" problems with NSIS based installers?
0014716 or 0010257 or one of their related bugs ...? |
|
|
(0039001)
|
kdawgud
|
2015-06-29 13:23
(edited on: 2015-06-29 13:25) |
|
I tried this on a couple computers and get the same results. One has a path > 1300. The other is much shorter around 600.
I also don't see the pop-up: "Warning! PATH too long installer unable to modify PATH!". Everything appears to work fine, but then the path doesn't change.
|
|
|
(0042802)
|
Kitware Robot
|
2016-06-10 14:29
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
|