-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't build on OS X #4
Comments
I'm not up on the terms of the iphone app store, but my understanding is that the reason they won't allow V8 would also block spidermonkey (and thus spidernode). |
jhford. This is not so. Apps using iMonkey have already been approved by Apple. iMonkey is a component of CouchDB which has been approved to run on iOS |
Well in any case, I'd at least want to get this SpiderNode compiled on my mac, so I can try it out with NodObjC at the very least. |
@TooTallNate: It builds but your issue above is that you need autoconf2.13 which can be built using macports. The build emitted a number of warnings but I have not yet looked at any of these. One thing was that the build will clobber your system node so best to build with a prefix to run it from the build location. I think I had expected to use 'spidernode' as opposed to 'node' on the commandline. |
I thought that for a second, but I'm fact he has autoconf. Because there are many names for the autoconf binary when versioned, I added a quick hack to invoke all three that I know with || between them. He has autoconf installed at version 2.13 but it's failing inside of autoconf |
(silly phone causing silly typos) |
@jhford. Hi. My initial build failed with same issue as TooTallNate. I thought I had autoconf2.13 on the system also since I use it in other builds but had forgotten it was not on that particular OS. I have multiple MacOSX installs on this dev machine. In any case, installed autoconf213 from macports and it built. What is involved in bringing the spidernode up date to track current node. Thanks |
@fairwinds The first step to bringing this up to date is probably going to be to bring v8monkey up to date. There are v8 apis that are being used that haven't been implemented yet in our api layer. There's also work to fix some things post-update to spidermonkey (we really have to track 3 different projects to make all of this work!). There are a couple issues files on v8monkey for that. That's really step 1, then attempting to build node with that is step 2. |
I would love to get this working to compile on my iPhone, and use node there (see https://tootallnate.net/nodejs-on-ios). The problem with the current node on iOS is that there's no way that Apple is currently gonna let V8 on their platform, so in the meantime we could potentially use SpiderNode on the app store.
I'm using 10.7.2 Lion:
The text was updated successfully, but these errors were encountered: