Apologies if this is not specific to this extension. I'm working on a HaxeFlixel project and trying to figure out where responsibilities end for each piece of this setup.
I am trying to get a dev environment set up. I can currently launch my project through the build task in tasks.json:
And if I look at Example.swf's permissions I now see:
-rw-r--r-- 1 chris staff 707K Jul 9 17:53 Example.swf
Essentially, missing the '@' sign and seemingly, the permission to execute. Any idea how to make the launch configuration create the .swf with the proper permissions, assuming that is the problem?
Apologies if this is not specific to this extension. I'm working on a HaxeFlixel project and trying to figure out where responsibilities end for each piece of this setup.
I am trying to get a dev environment set up. I can currently launch my project through the build task in tasks.json:
I'm using the Flash / Debug target. This creates my Flash .swf file and opens it immediately.
In the terminal output, I see
If I run
in the bin directory, I'll see this:
Now, I am trying to get debugging set up. For simplicity, I am removing that .swf file before running the Build + Debug launch config:
This config prints the following in the terminal tab, but does not launch the .swf.
And in the debug console I see
And if I look at Example.swf's permissions I now see:
Essentially, missing the '@' sign and seemingly, the permission to execute. Any idea how to make the launch configuration create the .swf with the proper permissions, assuming that is the problem?