Compiling with nw-gyp? about nodobjc HOT 6 OPEN

Is there way to "rebuild" all modules in a project?

@marcfowler figured something out here:
nwjs/nw.js#1811 (comment)

from nodobjc.

@reggi, the packages seem to be using an older version of nodobjc (0.0.15). The current is 1.0. Perhaps TooTallNate may be able to chime in here, but there's no need to build anything in nodobjc.

Maybe its a dependency of nodobjc that's not playing well with node-webkit OR its possible its accidentally pulling in 1.0 instead of 0.0.15?.. not sure.

from nodobjc.

@reggi Sorry for late response. Did you ever get this figured out?

from nodobjc.

No, I never had any luck with the (current) version of node-webkit when I tried recently. There has been some movement over in the other thread though: nwjs/nw.js#1811 (comment) I don't know if this will help though, I'll check as soon as I can get to it. Looks like a fork of node-ffi to help?

from nodobjc.

@TooTallNate @marcfowler I never figured out a solution for using the module I needed I just made another script (a workaround) for setting the background in osx using node-osascript. Plus I moved to atom-shell, which had the issue as well.

var osascript = require('node-osascript');

module.exports = osxBackgroundGet;

function osxBackgroundGet(callback) {
  osascript.execute([
    'tell application ``System Events"',
    'tell current desktop',
    'get picture',
    'end tell',
    'end tell'
  ].join("\n"), callback);
}

But I could still see this being an issue with some modules & node-webkit / atom-shell.

from nodobjc.

Just felt like I need to say that NodObjC builds fine with nw-gyp using nwjs 0.12.2. Only ref and ffi need to be rebuilt. The example "Hello World" application then works. Seems like $.NSApplication('sharedApplication') returns a new application; I was not able to get nwjs's own NSApp.

from nodobjc.