Rustup breaks this package about rust-enhanced HOT 5 CLOSED

I don't believe path is a known variable for build systems.

With any luck, the next dev build of ST3 will actually have code to pull in your shell environment on OS X, which should resolve this issue.

from rust-enhanced.

Thanks for the quick response @wbond !
So I'm assuming path will just be the user's system path when running build? (in the new fix, btw do you have a link for that?) which means we can get rid of the path field here?

from rust-enhanced.

@Jayflux see the env key described here: http://docs.sublimetext.info/en/latest/reference/build_systems/exec.html. Basically,

{
    ...
    "env": {
        "path": "$path:~/.cargo/bin"
    }
}

Disregard this, I got baited by @wbond. 😺

from rust-enhanced.

Apparently the path in the debug information is incorrect:
sublimehq/sublime_text#1039

from rust-enhanced.

Sorry, I was looking at the C++ part of the build system implementation… it does appear that through the kwargs in the exec build system that path should work. It does appear, however that it is not reflected in the build system output.

I'll try to get these edge cases cleaned up in one of the next builds.

from rust-enhanced.