H 15.0.244.16 + ST2 on OSX: Can't seem to get the build system to work

[bonsak]

Using Build system VEX Build. Runs fine and reports finished in the ST shell, but produces no *.vex file.
Is it because of the minor-minor version 16 at the end of the folder name?
Or is there another trick?

-b

[bonsak]

Bin path on osx is actually /Library/Frameworks/Houdini.framework/Versions/#.#.#/Resources/bin.
The build system tries to find it under /Applications/Houdini #.#.#

[bonsak]

Fixed OSX_DEFAULT, osx specific regex and the vcc bin path. But i'm still getting 'vcc: Error 1095: No input files specified.' when running 'compile and run.py' directly from the console. Doesn't work inside ST2 either. No error's but produces no vex file so probably same error.
Not sure what's wrong. I'll keep testing.
bonsak@5dc3025

[WhileRomeBurns]

Well, you've got it finding the compiler which is good but the path to the vex script is probably wrong or ill-formed. Definitely a bug. The file you're trying to compile is saved, right? You're not just running the command in a new tab?

I'll try and take a look at this over the weekend. The entire package is due an update for H15 so I'll get those changes in as well. I don't have OSX installed on any machines atm so there may be some back and forth before I get it right.

[bonsak]

The weird thing is that i'm doing os.path.exists() on vfl, vex and vcc inside the build method and both vfl and vcc are good.

So i tried to set the shell arg in subprocess.call([vcc, vfl, '-o', vex], shell=False)to false, and then i get vcc to output the correct vex file when running python compile_and_run.py with out any errors.

The build system still doesn't work though so i'm suspecting it has something to do with how VEX Build.sublime-buildis set up. Maybe :)

[bonsak]

Not sure if the PR is in line with your idea of doing everything from "compile_and_run.py" and it might be a little hacky. But it works :)