Tools.hxml missing

[Mcknight231]

He guys, so when I try to run the command haxelib run lime flixel, this error shows up:

Error: Could not process argument tools.hxml (file not found)
Invalid character:

Any help is appreciated

[player-03]

Did you download Lime from git? Not sure why else it would need to rebuild tools. But either way, it ought to be able to find tools.hxml.

Try these commands next:

• haxelib run lime --version
• haxelib run lime setup

[Mcknight231]

No, I did not download it from git, should I though?

[Mcknight231]

All of them say the same thing:

Error: Could not process argument tools.hxml (file not found)
Invalid character:

[tobil4sk]

Run haxelib libpath lime, which will give you the path to your lime installation. Navigate to that folder and check if there is a tools folder that contains a tools.hxml. If not, then perhaps lime has not installed correctly, try reinstalling it.

[Mcknight231]

It does have a folder called tools, and yet there is a file called tools.hxml. So idk why it says that, I tried reinstalling and that didn't work, perhaps I need to install it through github?

[Mcknight231]

I think I have an idea, maybe I should download from github? I think it has more compiled code.

[tobil4sk]

Lime installed from haxelib should still work properly. What version does it show if you run: haxelib list lime?

Is your lime install in the default location? Should be C:\HaxeToolkit\haxe\lib\lime\x,x,x\. If it's somewhere else maybe there is a permission issue, where some access rights are preventing haxe from being able to see the tools.hxml file.

You can also try haxelib run lime setup -v to get verbose output.

[Mcknight231]

Mine is 8.2.1, but the file directory is: C:\Windows\HaxeLib\haxe\lime\8.2.1, there is no folder called lib.

[tobil4sk]

I don't think it's a good idea to have it in the C:\Windows folder. Try moving your haxelib repository somewhere else, e.g. haxelib setup C:\HaxeToolkit\haxe\lib (you should move C:\Windows\HaxeLib\haxe there first if you want to keep your current library installs).

[Mcknight231]

My filepath is already C:\HaxeToolkit\haxe, yet there is no folder called lib, should I create one?

[Mcknight231]

Okay, so I've put all of library installs to the lib folder, but it still doesn't work. Any solutions?

[tobil4sk]

So haxelib libpath lime now says C:\HaxeToolkit\haxe\lib\lime\8,2,1\, correct? To confirm, did you reinstall lime after changing the lib folder?

[Mcknight231]

Yes the path is correct, no I did not reinstall lime after changing the lib folder.

[tobil4sk]

Try reinstalling lime again one more time. Then run haxelib run lime setup -v

[Mcknight231]

:\

[Mcknight231]

Maybe I should add lime to the environment PATH variable?

[joshtynjala]

If I had to guess, it can't find tools/tools.n, and it's trying to rebuild tools which is why it is referencing tools.hxml. That's weird because Lime from Haxelib definitely includes tools/tools.n. Looking at RunScript.hx, the only way that finding tools/tools.n wouldn't work with the if (!FileSystem.exists("tools/tools.n") code is if the current working directory were wrong, which is really odd. This to me seems like a larger issue than just Lime, and maybe something is broken in the Haxe installation.

I think that you should uninstall Haxe, delete the C:\HaxeToolkit directory completely, and then reinstall Haxe and Lime from scratch. Make sure to install Haxe to the default location of C:\HaxeToolkit, and not anywhere else like C:\Windows or C:\Program Files. Similarly, use the default path for Haxelib too. Then, try to install Lime again.

[player-03]

Also try running tools.n manually. cd into the tools directory, then run neko tools.n.

[Mcknight231]

This is what it says

[Mcknight231]

Anyone find any solutions yet?

[dimensionscape]

Anyone find any solutions yet?

It sounds like your environment is probably messed up somehow. Do what Josh recommended and start with a fresh haxe and lime dev environment. I don't think anyone can reproduce the problems you're having, including myself.

[Mcknight231]

I did that 3 times, and the problem still persists, idk what to do anymore