Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NEKOPATH env var not set after fresh install on Windows 10 ("missing neko.dll") #9021

Closed
benblo opened this issue Dec 10, 2019 · 3 comments
Closed

Comments

@benblo
Copy link

@benblo benblo commented Dec 10, 2019

I just installed Haxe 4.0.3 for the first time ever, using the Win64 installer from the official site (https://haxe.org/download/file/4.0.3/haxe-4.0.3-win64.exe/), I did not use the suggested install path (C:\HaxeToolkit) but instead C:\Work\Haxe\HaxeToolkit.

Opened a terminal, ran haxe: not found, haxelib: not found. I navigated to the install path, saw the haxe subfolder, ran haxe from there: ok, ran haxelib: got a "missing neko.dll" error.
Went to the neko folder, ran neko: ok.

Rebooted my PC, opened a terminal, ran haxe: ok, it's found now (the HAXEPATH env var must need a restart to properly propagate... meh), but when I ran haxelib I still got a "missing neko.dll" error.

So I manually set NEKOPATH = C:\Work\Haxe\HaxeToolkit\neko, then added %NEKOPATH% to PATH, rebooted again... finally, haxelib runs!

Not a big deal, but not a great first-time experience either :/ ...

@RealyUniqueName

This comment has been minimized.

Copy link
Member

@RealyUniqueName RealyUniqueName commented Dec 10, 2019

What's your windows version?
Did you run the installer with admin privileges or did it ask the permission during the installation?

@RealyUniqueName

This comment has been minimized.

Copy link
Member

@RealyUniqueName RealyUniqueName commented Dec 10, 2019

Ok, I've found the reason. Fix incoming.
Thanks for the report.

@josephsmendoza

This comment has been minimized.

Copy link

@josephsmendoza josephsmendoza commented Dec 11, 2019

So I manually set NEKOPATH = C:\Work\Haxe\HaxeToolkit\neko, then added %NEKOPATH% to PATH, rebooted again... finally, haxelib runs!

I found that %NEKO_HOMEPATH% was set and in the path, renaming it and its path entry to %NEKOPATH% fixed it for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.