-
Notifications
You must be signed in to change notification settings - Fork 7.3k
support building via xcode for mac #4020
Comments
The first trivial fix is to comment out To build successfully first build the I am working on trying to figure out why the dependency chain isn't working properly, and also a pull request that adds an option to configure and Makefile |
This would be sweet if the gyp XCode build supports real fat binary compilations. That would cut down on the package build times a lot and make @isaacs' life easier. The only problem I see there is that we hard-code |
@TooTallNate #4022 is certainly a step towards getting "proper" fat binaries, but since gyp is still generating the project files I think we'll have to figure out a way to manually generate a configuration that includes fat |
progress? |
@TooTallNate the stumbling block to fat binaries in a single compilation pass is the fact that openssl includes different files based on target arch, so openssl would need to be built twice and lipo'd to support using it in the linking pass for node. |
This commit: tjfontaine@61578c6 keeps being blown away since it's not been upstreamed, and maybe it never will be. As an alternative we could do this: There's some more discussion here: https://groups.google.com/forum/?hl=en%3Fhl%3Den&fromgroups=#!topic/nodejs/87svGdbbH0s |
That seems like a good solution, I will verify today and hopefully have that fixed |
@paddybyers I've submitted your change as a pr (#5209) with a slightly reworded commit log |
@tjfontaine: thanks |
I'm going to go ahead and close this, works the same as before, just build postmortem first |
chrome uses xcode for mac builds - we should too
cc @tjfontaine @TooTallNate @isaacs
The text was updated successfully, but these errors were encountered: