Add manual installation instructions

[waneck]

This is just so I don't forget about it; I'll handle it.

[ncannasse]

I think we should provide an install script and not rely on neko being installed on the machine

[waneck]

The best scenario will be to actually provide packages to the most used distros, and a fallback script + manual install instructions. I still don't remember the problem with using haxe --run, but I remember it broke something

[lostfictions]

I'm here by way of HaxeFoundation/haxe#3662. Pretty baffling to download a binary version of Haxe and have it complain about missing shared libraries. (Especially when the alternatives on Ubuntu are a badly-out-of-date package or a broken PPA.)

I ended up building from source, but I think for a lot of potential users that's kind of saying "I don't want you to use this software."

[ovidiugabriel]

Redirected from HaxeFoundation/haxe#4438 :

Yes, it will be nice to write down somewhere that haxelib depends on a manual installation of neko. Thanks!

[back2dos]

As explained before, with hxcpp and hxjava both relying on haxelib and therefore on neko, I think it is best to consider neko a haxe dependency and act accordingly.

[markknol]

I hope this is done, otherwise feel free to reopen.

[sonygod]

hello ,it's seem no haxe install on Centos 7 platform guide for install?

[Mariosyian]

What's the status of this? I downloaded the Linux 64-bit Binaries from the Haxe downloads page, and run into the infamous haxelib: error while loading shared libraries: libneko.so.2: cannot open shared object file: No such file or directory error.

After this I simply run sudo apt install neko and it immediately worked. I assume the same would need to be done in Windows, and if both were installed using binaries, then the PATH variable would need to be modified so one finds the other. This would be a really nice disclaimer to have in one of the README files (I suppose the one in the haxelib repo is the most appropriate).

As a noob myself, it's quite frustrating when the official documentation doesn't mention anything about this which I assume is the most common issue of installing Haxe via the binaries. Even more so, considering Neko is a project of the same company. Considering the Neko project is marked as deprecated, are there plans for future versions of Haxe to not require it at all, or have it baked in?