HaxePunk completion
manveru opened this issue · 8 comments
Similar to the NME completion issue in general, I guess, but completion for a newly created HaxePunk project doesn't work for me, the targets I'm trying to build for are android and linux.
I tried creating an .hxml using
haxelib run nme display android -hxml > android.hxml
and used that, as well as the .hxml files created by the build process, either way completion fails with the buffer jumping to files all over the system and spitting out missing class or var or other errors.
This is on Archlinux.
I'll check this out, thanks
I got a newly created haxepunk project working with this build.hxml. Note that I couldn't get it to compile with -D nme_install_tool, not sure what the problem is. However, there were no UInt, etc. errors:
-main Main
-lib nme
-lib HaxePunk
-cp src
-cp /usr/lib/haxe/lib/nme/3,5,4/
-cp /usr/lib/haxe/lib/HaxePunk/2,0,2/
#-D nme_install_tool
-D APP_COMPANY
-D android
-D mobile
-cp bin/android/haxe
-cpp bin/android/obj
--remap flash:nme
--remap browser:native
-D android
One other thought: what is your hxml file returned by:
:vaxe#CurrentBuild()
:vaxe#CurrentBuild() is not an editor command. I chose the .hxml using :ProjectHxml.
Sorry, should've been:
:echo vaxe#CurrentBuild()
I added a note in the docs about adding the output to a statusline.
If you chose using ProjectHxml, then that should've done it for you.
Are you on haxe 2.10? Is your project compiling in another editor?
The project builds fine with haxelib run nme test android for example.
Completion also works fine with https://github.com/clemos/haxe-sublime2-bundle without anything but the freshly created project, so for now I'll stick with that.
Haxe is 2.10.
That said, completion still fails in vaxe even with your hxml 😞
You do need to run nme build before you can start building/debugging from haxe. That was my problem.
But, that's not the problem you are seeing. What happens if you just run "haxe android.hxml"? That builds successfully?
If not, what does:
:set makeprg
tell you?
Finally, if you are able to build the file from within vaxe (:make), then can you give me some debug info? Turn the logging on:
:let g:vaxe_logging=1
and then trigger a completion somewhere. Then, open the message list (:msg). It should contain the build/display string, and whatever output that haxe returns. Send whatever you can from that message, and I'll try to figure out what happened.
I've added a bunch of nme options for vaxe. I can successfully build nme projects, such as the haxepunk examples. Completions are working as well. I'll close this, you can reopen it if you have any problems.