This change is only on Subversion right now, but I wanted to share briefly about a new feature I added to the NME command line tools.
If you execute “haxelib run nme setup” from a command-line or terminal, it will add a script to your PATH (in the Haxe directory) that shortens the command string. Instead of having to call “haxelib run nme”, you can simply call “nme”.
This is a minor change, but if you’re working from a terminal, this may help save your fingers. In the future, I would like to have an NME installer, which will set this up automatically.
While most of the supported targets for NME work automatically, some targets — particularly Android — will not work unless some variables are set. In the past, it might have been possible to try and build NME for Android, only to receive a compiler error. Now it will throw an error that prompts you to run “nme android setup” first.
It’s simple, but I think it should help eliminate confusion. When you run “nme android setup”, it will prompt you for the path to your Android SDK, Android NDK, Apache Ant and Java JDK directories. If you hit enter instead of typing a value, it will keep the original. If the value was set in your system variables, it will leave them there and will not write a new copy in your .hxcpp_config.xml file.
The command will update your .hxcpp_config.xml automatically. It will preserve any custom include paths you set for HXCPP, as well as other defines you may have had set in the file.
There are other changes that have happened (and will happen), even since the recent 3.1 beta 2 release, but this was a little tidbit that I thought was worth mentioning. If you have more ideas for making NME even easier to install and use, we would love to hear all your suggestions here, on the forums, or on the mailing list.