OSX npm install fails

[stephenheron]

Hi,

I am attempting to install using:

npm install node-core-audio

but I am getting a error stating:

/Users/stephen/node_modules/node-core-audio/NodeCoreAudio/targetver.h:8:10: fatal error:    'SDKDDKVer.h' file not found

Any ideas on what the issue is?

Thanks, Stephen

[ZECTBynmo]

Try cloning the repository and doing "npm install ." inside of the project directory. The version that's currently up on the npm registry is older, and only works for Windows. I guess I should probably push up the new version sooner than later...

[stephenheron]

Ah thanks,

That at least got it installed.

I had another issue but I can't remember the exact error message but to get it working I had to move

node-core-audio/build/Release to node-core-audio/build/Debug.

[ZECTBynmo]

Ah, inside of node-core-audio.js, it's looking for the debug version of the C++ extension. If you want to build debug, run "node-gyp configure --debug" and then node-gyp build". If you want to use the release version (which was built automatically from the npm install) you can change the path in node-core-audio.js, or move the .node file like you did.

[stephenheron]

Hi,

Thanks for the quick responses. Got everything working now!

Enjoying using the module thanks for putting it together.

[sberryman]

Any updates on pushing a fixed OSX version to NPM?

[ZECTBynmo]

I feel bad pushing something that's so shaky to npm, so I've been hesitating for months. I really want to get this project going, but it's so hard to find time for it.

Do you really think I should? Would it help you to have it up there? I can find some time if it really matters.

[sberryman]

It would just make it easier for people to get going and try out the project if it works on OSX. It is a pain digging through issues (especially closed) to try and get something working. To use the project you pretty much have to clone it, npm install and change the path to Release. I would update the readme to show that as the install process and remove it from NPM or make the necessary changes and publish. Just my opinion for what it's worth...

[ZECTBynmo]

Thanks for the response, you're right, it must be difficult to approach this project right now. I'll reopen this issue so people can see it, and hopefully find time to update the npm module in the near future.

[ZECTBynmo]

A new version of the npm module is out, and hopefully building. Please let me know if you're seeing any issues.

[jackaperkins]

I'm doing npm install on osx 10.8.4 and make is failing thusly: ld: library not found for -lportaudio clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [Release/NodeCoreAudio.node] Error 1

is this portaudio library something i need to include manually elsewhere on the system? I'm very much a novice with compilers and the like, thanks for your patience.

EDIT

I'm dumb and didn't notice the incredibly obvious readme.md instructions, i skipped and was looking on @ZECTBynmo 's hosted version. Durp.

[ZECTBynmo]

Did you get things up and running in the end Jack?

[Fishrock123]

I installed portaudio via sudo port install portaudio, and I'm still getting Jack's error:

ld: library not found for -lportaudio
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/NodeCoreAudio.node] Error 1

[ZECTBynmo]

Unfortunately I don't have a mac (I've been doing all this blind) so I can't try it on my end. Did you verify that the library was actually installed? Is it in your PATH?

[Fishrock123]

I'm not really sure. macports says it is installed.

My PATH file-y thing looks like:

/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin

Edit: I've been looking into portaudio and gyp and I'm going to try and get it to be able to just include the lib files, like the windows one, if at all possible.