Mac: 'flixel' command does not work in OS X about flixel-tools

[impaler]

Thanks for testing Tiago its been working on 10.8.4 fine for me, what happened when you ran the haxelib run flixel-tools setup command?

What does haxelib run flixel-tools give you?

The tools work just like the openfl tools in that it just copies a simple bash script that alias' the haxelib run flixel-tools command. You can see here https://github.com/HaxeFlixel/flixel-tools/blob/dev/src/commands/SetupCommand.hx there will be no need to make a script executable manually as its using haxelib like this.

[Tiago-Ling]

For some reason, the bash script don't work for me. the base does not
recognize the command:

You have now setup HaxeFlixel Tools
*
*

• Try the 'flixel' command to test it :)*
  *
  *
  Sublime Text
  new-host-4:~ tiagolingalexandre$ flixel
  -bash: flixel: command not found

Running 'haxelib run flixel-tools' does work normally, but it seems the
bash script doesn't get linked.

The lib is located in /usr/lib/haxe/lib/flixel-tools
The script is in /usr/lib/haxe/lib/flixel-tools/git/bin/flixel.sh

Tiago Ling Alexandre
Tel: [phone]

2013/7/26 impaler [email protected]

Thanks for testing Tiago its been working on 10.8.4 fine for me, what
happened when you ran the haxelib run flixel-tools setup command?

What does haxelib run flixel-tools give you?

The tools work just like the openfl tools in that it just copies a simple
bash script that alias' the haxelib run flixel-tools command. You can see
here
https://github.com/HaxeFlixel/flixel-tools/blob/dev/src/commands/SetupCommand.hxthere will be no need to make a script executable manually as its using
haxelib like this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-21657152
.

[impaler]

Why do you have a * character when using the command? just use flixel

[Tiago-Ling]

There's no * character, only 'flixel'

Tiago Ling Alexandre
Tel: [phone]

2013/7/26 impaler [email protected]

Why do you have a * character when using the command? just use flixel

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-21657529
.

[igrowbeards]

I'm having the exact same issue as @Tiago-Ling in exactly the same way as he describes it.

I followed the instructions in the readme and tested it several times just to be sure i was not just making an error on my end somewhere.

I'll be glad to help test changes on osx if you need it - just let me know.

[impaler]

I think this is fixed, sry error on my part by the looks of it.

[igrowbeards]

Confirmed. It's working fine now. That was quick, thanks! :)

[impaler]

Nice, please reopen if you have still have issues @Tiago-Ling

[Tiago-Ling]

Alright, after the latest update on the lib, everything is working fine.

Thanks impaler, the tools are awesome!

Tiago Ling Alexandre
Tel: [phone]

2013/7/27 impaler [email protected]

Nice, please reopen if you have still have issues @Tiago-Linghttps://github.com/Tiago-Ling

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-21659366
.

[bradparks]

hey... i just tried to install flixel-tools for the 1st time on a macbook pro, after doing a "haxelib upgrade", and I get the following after running the setup command with or without sudo.

$ sudo haxelib run flixel-tools setup
[file_contents,/usr/lib/haxe/lib/flixel-tools//.current]

then when I try and run "flixel" in the terminal, it fails like so:
$ flixel
-bash: flixel: command not found

[impaler]

Hello Brad, I am unable to reproduce this. What does haxelib run flixel-tools give you? also make sure your using the latest haxelib with haxelib selfupdate if your still having problems could you tell me your haxelib version and your haxelib list.

[bradparks]

hey! I did the haxelib selfupdate command like you suggested, and then reinstalled it from scratch and that fixed it.... i'd never heard of the "selfupdate" command.... nice! thanks for the help!

[misterkeeter]

I seem to be having this problem in OS x 10.9

[Gama11]

@misterkeeter I assume you already ran haxelib selfupdate? Also, which version of flixel-tools are you running? The one from haxelib or the latest version from git?

[misterkeeter]

@Gama11 I have run haxelib selfupdate. I have tried the haxelib version and the latest version from git.

[misterkeeter]

Looks like all i needed to do was to add an alias to my .bash_profile

flixel="sh /usr/lib/haxe/flixel/flixel.sh"

[impaler]

Strange @misterkeeter I havent needed to do this on mountain lion or linux, with flixel.sh being in your haxe folder it should work. So flixel didn't work after running haxelib run flixel-tools setup?

[misterkeeter]

@impaler yeah that's correct, after some more tinkering I did notice that flixel-tools setup creates an alias to the directory where flixel.sh is, instead of an alias to the flixel.sh file.