TooTallNate / node-speaker

Output PCM audio data to the speakers
648 stars 145 forks source link

node-gyp build fail on heroku #100

Open stephensong opened 7 years ago

stephensong commented 7 years ago

I am trying to use the node package web-audio-api in my heroku hosted app. I don't think I have any actual need for node-speaker, but it is a dependency of web-audio-api.

So after figuring out how to configure the apt buildback for heroku, I managed to get it to apt-get libasound2-dev, but alas, the build then fails with:

remote: -----> Building dependencies
remote:        Installing node modules (package.json)
remote:
remote:        > speaker@0.3.0 install  /tmp/build_2e93fb359eaf5b018caf9220af8ba9cd/node_modules/speaker
remote:        > node-gyp rebuild
remote:
remote:        make: Entering directory `/tmp/build_2e93fb359eaf5b018caf9220af8ba9cd/node_modules/speaker/build'
remote:        CC(target) Release/obj.target/output/deps/mpg123/src/output/alsa.o
remote:        ../deps/mpg123/src/output/alsa.c: In function ‘initialize_device’:
remote:        AR(target) Release/obj.target/deps/mpg123/liboutput.a
remote:        COPY Release/liboutput.a
remote:        CXX(target) Release/obj.target/binding/src/binding.o
remote:        SOLINK_MODULE(target) Release/obj.target/binding.node
remote:        /usr/bin/ld: cannot find -lasound
remote:        collect2: error: ld returned 1 exit status
remote:        make: *** [Release/obj.target/binding.node] Error 1
remote:        make: Leaving directory `/tmp/build_2e93fb359eaf5b018caf9220af8ba9cd/node_modules/speaker/build'

(I have removed a couple of spurious warnings from the above.)

The problem seems clear enough: the "ld cannot find -lasound" bit. But I've no clue how I might go about fixing it on Heroku. Can anybody here shine some much needed light on my problem?

many tias.