hashlink (0.1.0) contains the build tools to make it all work, similar to the hxcpp/hxcs/hxjava haxelib libraries required to compile with the cpp/cs/java haxe targets.
$ haxe -hl out/main.c -main Main
Code generated in out/main.c automatic native compilation not yet implemented
Though, seems like an unfortunate overloading of the name hashlink. Seems like that ought to be named “hxhashlink”, to better go with hxcpp, hxcs, and hxjava, no?
It looks like, for me, that the hashlink haxelib library isn’t actually required to generate the C code. You just have to add the no-compilation define ( -D no-compilation ) and it works without complaining. It still doesn’t do the native compilation for you, so you will have to write the makefiles or whatever you need, but it will generate the C code. Also the hashlink haxelib library hasn’t been published in two years so I think that it isn’t used anymore.
I found this out while testing and getting reference from the way that Armory3D uses HashLink.
Edit: Oops. Nevermind, now I get it. Like @ibilon said, the haxelib contains the build tools. They just aren’t implemented yet and the haxelib hasn’t been updated in a while.