[Error] "sh.exe": flixel: command not found" when typing "flixel" into the git bash. (Windows 7)

[Khranos Lucror]

Hello everybody! I'm new to Haxeflixel, but have been working with Haxe for a while now. I've been attempting to get Haxeflixel set up, but have been running into issues with the libraries.

Whenever I try to run the flixel command, it gives me the error "sh.exe": flixel: command not found". From what I've read, it's because the language hasn't installed. Whenever I send "haxelib list", I've got "flixel-tools" and "flixel" in said list (after running the appropriate install commands). I've gone through and deleted everything, and reinstalled each thing in the correct order, but I get that error each time.

If I try to run flixel.bat within my Haxetoolkit\haxe folder, it crashes instantly. I've even gone through to Haxetoolkit\haxe\lib\flixel-tools\(numbers here\bin and copied the .bat file (and shell to be sure) to the Haxetoolkit\haxe directory, to no avail (and I tried running said .bat before copying/pasting).

I run a 64 bit Windows 7 computer that I built, and haven't had any issues before. If a hardware spec is needed, I'll gladly retrieve it. 

Thank you for reading, and I'd love to solve this issue as soon as possible!

[Sebastian Fernandez]

Maybe the enviorement variables are not defined. Which haxe version do you have?

[Karl Penzhorn]

Have you run haxelib run flixel-tools setup ?

[Oliver Ross]

I was having the same problem myself, but settled for using cmd - but is working now.

First create new file '.bashrc'  in C:\Users\[your logon]\   This is loaded when git bash inits, and you can put functions and startup stuff in there

Then add this function to the .bashrc file : 

function flixel() {

haxelib run flixel-tools $1

}

So instead of calling the batch script in HaxeToolkit when you do 'flixel' it'll call the .bashrc function - which is pretty much identical, except how it gets the args

Hope that helps

[Khranos Lucror]

Thank you everybody for the answers (I posted this before heading out for the day, hence my late response), but I felt I'd try Oliver's answer first before proceeding. As it turns out, it worked perfectly! Hopefully this'll help other people as well, since this is a nasty error with a rather interesting solution that you'd probably not be able to create on the spot.

Thank you again!