:make not working in flixel project.

[IkonOne]

Issues

1. On editing a hx source file, Vaxe does not asks what LimeTarget to build for and this error is shown: Default build file not valid:
2. So, I do a LimeTarget and select flash. After make, it looks like the build happens, but the swf is incorrect. I tried verifying the build command via logging in vim but couldn't find it(am I just blind?).

Replication Steps

After creating a flixel project:

flixel tpl -n "flixelTest"

Open up the project in vim, edit a source file, LimeTarget and make. Here is a pastebin of a 'level 9' verbosity session doing just this.

Environment Details

Acer C720
Lubuntu piggy backing off of ChromeOS via Crouton
vi/vim/gvim all affected

Note

Creating a lime project an opening that in vim/vaxe on this setup works perfectly. Which would lead me to think the issue is with ChromeOS/Crouton/Lubuntu because this exact same process works perfectly on my mac and windows machines.

[jdonaldson]

Sorry for the delay, you can enable some logging in vaxe with:

:VaxeToggleLogging

This will dump the haxe build commands into the :messages screen. Can you take a look there and see if anything looks off?

[eshcherbin]

Maybe renaming the autogenerated 'Project.xml' to 'project.xml' will resolve the problem.
At least it's helped me with a similar problem.

[IkonOne]

Hey Guys, I'm sorry I'm just now responding. I will try and check this
when I get home tonight.

On Tue, Apr 28, 2015 at 8:25 AM, Egor Shcherbin notifications@github.com
wrote:

Maybe renaming the autogenerated 'Project.xml' to 'project.xml' will
resolve the problem.
At least it's helped me with a similar problem.

—
Reply to this email directly or view it on GitHub
#70 (comment).

[jdonaldson]

ah, is it a capitalization issue? I have a config parameter that specifies how vaxe identifies build configs... project.xml is one of the defaults. I'll see about making this case-insensitive.

[jdonaldson]

Hmm... it turns out the vim glob statement I use is case sensitive on linux, and there's no straightforward way of making it insensitive. I'll have to see if someone else has come up with a workaround, that's too low level for me to want to support.

[IkonOne]

I have finally found my machine and it is currently not set up with linux on it. I won't be able to test this in the foreseeable future due to the time it will take to get back up and running. It may be worth simply closing it and I will re-open if I ever am able to get to a point where I can provide a meaningful contribution.

[jdonaldson]

I'm fine with leaving this open. I don't think open issues are a bad thing for a repo.