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
Various errors when using haxelib from 3.1.3 in Ubuntu 14.04.2 #3924
Comments
Using Haxe 3.1.3 with git haxelib is not a good idea. |
I was just trying to use HaxeFlixel, and they recommend using haxelib for installing, as stated in http://haxeflixel.com/download/; so, how should I proceed? |
Can you try to run haxelib on a folder other than the haxe folder? |
Ok, ran haxelib in another folder, the last error persists: /usr/lib/haxe/extra/haxelib_src/src/tools/haxelib/Main.hx:715: characters 32-55 : Class<sys.FileSystem> has no field absolutePath It seems haxelib was indeed using files from the haxe directory, somehow. |
That's because the |
Thanks, this solved the issue, now haxelib is working as intended. Since there is no problem with the code itself and it was all caused by running a git checkout 3.1.3 and "misaligning" the repos, I'll close this issue. Also, thanks for the speedy responses, this further motivates me to use Haxe :-) |
Steps:
Output:
/usr/lib/haxe/std/neko/_std/sys/io/FileInput.hx:60: characters 26-29 : Invalid package : std should be
std/Type.hx:32: characters 1-30 : Invalid package : std should be
std/Type.hx:33: characters 1-28 : Invalid package : std should be
std/Type.hx:64: characters 15-65 : Invalid package : std should be
std/Type.hx:94: characters 15-68 : Invalid package : std should be
std/Type.hx:159: characters 15-86 : Invalid package : std should be
/usr/lib/haxe/extra/haxelib_src/src/tools/haxelib/Main.hx:715: characters 32-55 : Class<sys.FileSystem> has no field absolutePath
Issue #3670 says that the first error line is caused by neko missing, but I've installed the Ubuntu version (2.0.0-3) to no avail. As for the other lines, I couldn't find anything.
The text was updated successfully, but these errors were encountered: