Skip to content

Wrong permissions on output binary when using launch.json build + debug configuration? #57

@PhoenixWright

Description

@PhoenixWright

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:

{
    "type": "lime",
    "command": "test",
    "group": {
        "kind": "build",
        "isDefault": true
    }
}

I'm using the Flash / Debug target. This creates my Flash .swf file and opens it immediately.

In the terminal output, I see

> Executing task: lime test flash -debug -Dfdb --connect 6000 <

If I run

ls -hartl

in the bin directory, I'll see this:

-rw-r--r--@ 1 chris  staff   707K Jul  9 17:50 Example.swf

Now, I am trying to get debugging set up. For simplicity, I am removing that .swf file before running the Build + Debug launch config:

{
    "name": "Build + Debug",
    "type": "lime",
    "request": "launch"
}

This config prints the following in the terminal tab, but does not launch the .swf.

> Executing task: lime build flash -debug -Dfdb --connect 6000 <

And in the debug console I see

running /Users/chris/Documents/Development/Example/export/flash/bin/Example.swf
Error: Command failed: "/Users/chris/Documents/Development/Example/export/flash/bin/Example.swf"
/bin/sh: /Users/chris/Documents/Development/Example/export/flash/bin/Example.swf: Permission denied

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions