GetStream
Adding the package results in an error. No compatible binary build found for this package
Hey! Really excited that stream now has a meteor package as well.
I can't add the package though. Whenever I try to I get this message:
While checking for getstream:[email protected]: error: No compatible binary build found for this package. Contact the package author and ask them to publish it for your platform.
Hope someone can help out :)
Hi @novamul what platform (linux?) are you trying to install stream-meteor on?
@novamul ok i investigated and it seems the binary dependencies aren't build correctly on the Windows platform. I will need some more time to find out if there is a solution to this problem.
Ok, too bad. Thanks for your quick responses and effort. I hope it can be fixed.
Hi @matthisk. This is currently a blocking issue for us. Is there anything we can do to help? I searched around but cannot find the source code of getstream:bin-deps.
@lewtds try running meteor publish-for-arch getstream:[email protected] on a Windows machine, I have tried this but it results in an error message. Unfortunately I haven't gotten around to debugging this error message. The gestream:bin-deps project is currently not on github I will try to create a repo for it so we can fix this issue.
Looks like node-fibers failed to build because most Windows machines don't come with VC++ and Python (and somehow the prebuilt binary is not used). Do we really need that package? I thought Meteor is already running on fibers?
We managed to remove the bin-deps dependency and make it work by just Npm.require-ing fibers/future and getstream directly from this package (Meteor comes bundled with fibers already). Will try to upstream the changes ASAP.
That wouldn't change the issue though would it? You still need to build the 'fibers' npm package for all target machines (i.e. linux/osx/windows). You can not use the fibers bundled with Meteor as far as I know? If you want to use fibers/futures you have to retrieve them from npm. I separated the npm dependencies into a different meteor package to avoid having to rebuild for every target architecture when I update stream-meteor. I will retry to build getstream-bin-deps for windows with build tools installed.
Hi @matthisk I just bumped into this problem when I was porting an app to Meteor Galaxy hosting ( running Ubuntu 14.04). Don't suppose you've had the chance to look more into it? I'm getting a slightly different error when I build:
=> Errors while initializing project:
While checking for getstream:[email protected]: error: No compatible binary build found for this package. Contact the package author and ask them to publish it for your platform.
Thanks!
Hi @kantle and @matthisk - I've encountered this one myself.
Take a look at this:
http://docs.meteor.com/#/full/meteorpublishforarch
Meteor packages must be published for each platform you want to run them on:
"Currently, the supported architectures for Meteor are 32-bit Linux, 64-bit Linux and Mac OS. Galaxy's servers run 64-bit Linux."
Hi @ErikAugust - that's interesting. I've been running the app successfully on Digital Ocean, which is also running Ubuntu 14.04 x64. Shouldn't the package also fail on DO if it didn't support 64 bit?
Hi guys maybe I did something wrong on the latest release (you have to do "publish for arch" for every release), I will make sure it is published for all architectures.
Btw Windows built is still broken (@erik are you on Windows or OS X?), I can not get the package to build on windows and the Meteor support is also of no assistence
Thanks for taking a look @matthisk - just for more info I'm on OSX. I was able to deploy to Digital Ocean using MUP without a problem. I tried removing the GetStream package and was able to deploy to Galaxy as well - so there is something about the deploy process to Galaxy that is not interacting well with this version of the package.
@matthisk - Thanks, I'm on OS X like @kantle.
I have forked this library and have it installed locally - and will be taking a look at a solution this weekend.
Thanks again!
@matthisk @ErikAugust I downgraded this package to version 0.3.7 and was able to build and deploy just fine to Galaxy, so I think it has something to do with how version 0.4.0 was published.
@kantle @ErikAugust I just build the package for linxu (x86 and x64) so everything should work as expected. Please let me know if you are still experiencing any issues.
Awesome - just upgraded back to 0.4.0 and deployed no problem. Thanks @matthisk!
Hey Guys! Read through the above thread. Did a Windows fix ever get implemented? Hitting the "No compatible binary build found for this package."
No currently we do not have a solution for this. Support from Meteor publishforarc on Windows doesn't seem to be in great shape. I am unable to use their architecture to publish the package. I tried running the build on a VM windows machine without success. I will give their build farm a try again right now, maybe they have applied some fixes to their architecture.
