Open rcastill opened 6 years ago
@rcastill Thanks for trying this out. When we added macOS support a while back (April 2017), we only did the work to support the native (C) components and the Java binding. We later added support for out-of-proc Java modules too. We'd like to add support for Node.js and .NET Core modules also, but we haven't been able to allocate the time/resources to do it. The work shouldn't be difficult--probably just fixing a few little hang-ups like the issues you encountered--but we just haven't done it yet.
So the next step would, in fact, be to (1) update build_nodejs.sh to copy dylibs in the macOS case, and (2) fix the build errors, as you suggested. We'd happily accept your contribution!
@damonbarry thanks for your answer, I'll see what I can do!
I'm trying to compile
/v1/samples/nodejs_simple_sample
under macOS, so I follow the instructions.I built nodejs running
/v1/tools/build_nodejs.sh
The script didn't finish well because it couldn't copy any
*.so
files from the/v1/build_nodejs/node/out/Release/lib
folder (there was a.dylib
instead). So I copied it into the/v1/build_nodejs/dist/lib
folder and made the symlinks.Then tried to build
iot-edge
with nodejs bindings by running:Full output
I tried to run
./tools/build.sh
with-cl -Wno-everything
and later-cl -w
with no success.I suppose my next attempt will be to patch that code, but it doesn't look like a good solution. Is this a known issue? is it macOS (clang) related?
Thanks in advance!