Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Windows Installer: automatically set path (for new programmer) #8870
Some background first, thanks for bearing with me.
I wanted to help an acquaintance get started learning programming (with Haxe as their first language). They are completely new to programming. They have access to an MS Windows machine (they have an account), but no admin access.
I thought the easiest path forward would be to use Haxe's Python target. (They don't need performance --- they just need a programming environment installed and working in the easiest way possible.)
I downloaded and installed Python 3.7.4. I have not used MS Windows for programming in years. I ran the Python installer, and it gave me a choice to install Python on the system or else locally (since I don't have admin access on this particular machine, I went for the local install, and it worked). It also gave me the choice of adding
Upon then installing Haxe, I was asked here as well where to install, and I don't think there was a default local location so I opted for c:/users/me/dev or somesuch. The installation completed, but when I opened up
To make it as easy as possible for new users to get started using Haxe on a MS Windows machine, I think it would be most helpful if the installer could set the path (like how the Python installer does) so that
Closed and re-opened
Rebooted as well. No joy.
Opened up "Advanced System Settings" --> Environment Variables, and there's a PATH in there (for me as a local user) with a bunch of Python additions, but nothing for Haxe.
This is a MS Windows 7 Pro PC. When I boot up the machine and log in I think it pulls my home directory (or whatever MS calls it) from a network drive.
When I installed Haxe I specified that it go into
The related installer code hasn't changed in years and has been working fine, so I can only assume that this is some problem that is specific to the user's setup. Maybe some access restrictions, Windows tends to be interesting in that regard.
For reference, the code being used for this comes from this little C snippet: https://github.com/HaxeFoundation/haxe/blob/development/extra/setup.cpp
This is generated as
The reason we're using this is because at the time, NSIS had some bug which would wipe your
Ok. Note, I'm not familiar with MS Windows cmd, so I'm not going to try to do
I've previously removed the installation by running the uninstaller app.
I just downloaded the 4.0.2 Windows 64-bit installer. Installed into c:/Users/me/opt. Installer seemed to finish fine. Opened up cmd but
Ok. Hope this report was useful. I still don't understand why the Python installer worked (for this local install) but Haxe's did not. It looks like the Python installer installed into c:/Users/me/AppData/Local .
You can try this build: https://build.haxe.org/builds/haxe/windows64-installer/haxe_2019-11-26_4.0_bugfix_1f85d5f.zip
By the way, before even trying that newer build, upon uninstalling the one I just installed, I get a note in the uninstaller that says, "Target was NOT found in PATH (nothing to remove)", with a popup dialog that says, "Could not write updated PATH to HKLM".