-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
doc: update build instructions for OS X #6309
Conversation
* You also need to install the `Command Line Tools` via Xcode. You can find this under the menu `Xcode -> Preferences -> Downloads` | ||
* This step will install `gcc` and the related toolchain containing `make` | ||
|
||
On FreeBSD and OpenBSD, you will also need: | ||
* libexecinfo (FreeBSD and OpenBSD only) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The (FreeBSD and OpenBSD only)
note seems a bit redundant now :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM |
1 similar comment
LGTM |
I think what might be slightly confusing is that Xcode install takes care of most all the build chain needed (except python) . Unless things have changed I remember that getting node to build on OSX was as simple as Might not have to include the section that suggest manually grabbing gcc and clang? What could potentially happen is a person could install xcode, then override clang version by accident manually and then the xcode will start complaining? |
|
||
On OS X, you will also need: | ||
* [Xcode](https://developer.apple.com/xcode/download/) | ||
* You also need to install the `Command Line Tools` via Xcode. You can find this under the menu `Xcode -> Preferences -> Downloads` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Long line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7da4fd4
to
c7066fb
Compare
3b54f1a
to
481d6ad
Compare
@wonderdogone You raise good points. I'm not sure what the best way to deal with it is. It might make sense to separate out OS X prerequisites entirely from *nix prerequisites. I think the current status of this PR is an improvement over the current document and am inclined to land this, and then work on (or let someone else work on) further improvements along those lines. Would you strongly disagree with any of that approach? |
|
||
On OS X, you will also need: | ||
* [Xcode](https://developer.apple.com/xcode/download/) | ||
* You also need to install the `Command Line Tools` via Xcode. You can find |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think xcode is optional; you can get the cli tools separately. Re-iterating my statement from this mornings call wrt me being a user not a osx expert, but something like xcode-select --install
could work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, to test this, we need a pristine OS X for someone to try it out on. Anyone? Anyone?
Does the OS X in CI build from scratch, more or less? If so, does it install XCode?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rvagg ^
(likely installed xcode)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happily, @thealphanerd volunteered to install a vanilla OS X VM and test whether build works without installing full XCode or not. Go, @thealphanerd!
Building Node.js on OS X requires XCode (because node-gyp requires XCode). Add that information to BUILDING.md. Additionally, this changes references to `Macintosh` in BUILDING.md to refer to `OS X`. This is consistent with the way other references are to operating system families (`Unix`, `Windows`) and not brand names or hardware architectures.
Looks Good To Me. |
Building Node.js on OS X requires XCode (because node-gyp requires XCode). Add that information to BUILDING.md. Additionally, this changes references to `Macintosh` in BUILDING.md to refer to `OS X`. This is consistent with the way other references are to operating system families (`Unix`, `Windows`) and not brand names or hardware architectures. PR-URL: nodejs#6309 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Landed in 153b796. Will open a new issue for some of the other things brought up in the conversation. |
agreed.. |
Building Node.js on OS X requires XCode (because node-gyp requires XCode). Add that information to BUILDING.md. Additionally, this changes references to `Macintosh` in BUILDING.md to refer to `OS X`. This is consistent with the way other references are to operating system families (`Unix`, `Windows`) and not brand names or hardware architectures. PR-URL: #6309 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Building Node.js on OS X requires XCode (because node-gyp requires XCode). Add that information to BUILDING.md. Additionally, this changes references to `Macintosh` in BUILDING.md to refer to `OS X`. This is consistent with the way other references are to operating system families (`Unix`, `Windows`) and not brand names or hardware architectures. PR-URL: #6309 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Building Node.js on OS X requires XCode (because node-gyp requires XCode). Add that information to BUILDING.md. Additionally, this changes references to `Macintosh` in BUILDING.md to refer to `OS X`. This is consistent with the way other references are to operating system families (`Unix`, `Windows`) and not brand names or hardware architectures. PR-URL: #6309 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Building Node.js on OS X requires XCode (because node-gyp requires XCode). Add that information to BUILDING.md. Additionally, this changes references to `Macintosh` in BUILDING.md to refer to `OS X`. This is consistent with the way other references are to operating system families (`Unix`, `Windows`) and not brand names or hardware architectures. PR-URL: #6309 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Checklist
Affected core subsystem(s)
doc build
Description of change
Building Node.js on OS X requires XCode (because node-gyp requires
XCode). Add that information to BUILDING.md.
Additionally, this changes references to
Macintosh
in BUILDING.md torefer to
OS X
. This is consistent with the way other references are tooperating system families (
Unix
,Windows
) and not brand names orhardware architectures.