This repository was archived by the owner on Apr 22, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
support building via xcode for mac #4020
Description
chrome uses xcode for mac builds - we should too
cc @tjfontaine @TooTallNate @isaacs
Activity
tjfontaine commentedon Sep 14, 2012
The first trivial fix is to comment out
'GCC_VERSION': '4.2',incommon.gypiTo build successfully first build the
postmortem-metadataconfiguration, thenAll (node)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
TooTallNate commentedon Sep 14, 2012
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
process.archvia a command-line define (-DARCH=x64), which wouldn't work so well if we were compiling both archs at once. We could introduce some "smart" logic to detect the proper arch in the source code like here: https://gist.github.com/3723332tjfontaine commentedon Sep 14, 2012
@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
ry commentedon Sep 22, 2012
progress?
tjfontaine commentedon Oct 25, 2012
@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.
paddybyers commentedon Apr 3, 2013
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:
paddybyers@9efd361
There's some more discussion here:
https://groups.google.com/forum/?hl=en%3Fhl%3Den&fromgroups=#!topic/nodejs/87svGdbbH0s
tjfontaine commentedon Apr 3, 2013
That seems like a good solution, I will verify today and hopefully have that fixed
tjfontaine commentedon Apr 3, 2013
@paddybyers I've submitted your change as a pr (#5209) with a slightly reworded commit log
paddybyers commentedon Apr 3, 2013
@tjfontaine: thanks
tjfontaine commentedon Dec 7, 2013
I'm going to go ahead and close this, works the same as before, just build postmortem first