Brad King wrote:
> I logged out and logged back in and
> then everything gets the proper PATH.
>
> Then I un-installed again and had to logout/login again to get the
> PATH updated for programs launched through shortcuts.
Hmm, I didn't do any logging out or in. Maybe that was the cause.
On 06/21/2016 03:37 PM, Brad King wrote:
Nils, the installers in question were produced from your WiX
installer work (thanks again for that!). Is this something wrong
with the 64-bit installer or simply a Windows/MSI subtlety/bug?
I can't try this out here right now but looking at the
On 06/20/2016 05:10 PM, Stephen Kelly wrote:
> * Install the CMake 3.6 RC 64 bit package
> ** The install location for CMake 3.6 RC 64 bit was not added to my PATH?
I just un-installed my 64-bit RC and re-installed it with the option
to manipulate the system PATH. At this point the PATH as
Brad King wrote:
> MSI
> takes care of reversing effects of the removed installation, so that
> may have removed it from your PATH.
Hmm, the steps I took were:
* Uninstall my pre-existing CMake 3.1 installation
* Install the CMake 3.5 32 bit package
** At this point everything worked on the
On 06/18/2016 08:12 AM, Stephen Kelly wrote:
> I tried the CMake 3.6 RC on Windows yesterday. I initially downloaded the 64
> bit version, and the installer uninstalled my CMake 3.5 (32 bit).
This is because the MSI package records only a single package name for
all CMake versions. Each
Hi,
I tried the CMake 3.6 RC on Windows yesterday. I initially downloaded the 64
bit version, and the installer uninstalled my CMake 3.5 (32 bit).
Then, in my 'Visual Studio 14 2015 64 bit command prompt', the cmake
executable was no longer found. I think the difference is that the 64 bit
