-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
remove the need for xcodebuild #1057
Conversation
I have removed all commands that use xcode build and there seems to be no issues. This means that we don't get the error message anymore.
You may need to ask upstream about this, honestly I have no idea whether this is a good idea or not. |
FYI, trying to push this upstream https://chromium-review.googlesource.com/c/492046/ voice your opinion |
According to @bnoordhuis in #1267 (comment) we don't pull things from GYP any more, therefore this should be good to land? |
This should also go into the copy of GYP vendored into node, to fix the |
I kicked off a dry run on the upstream CL, so we can at least benefit from their CI coverage. |
👍 , and if you think there's a chance you'll succeed in the upstreaming then I'm happy to do that, it just seems unlikely to ever make it back into node-gyp or node at this point. |
As for upstreaming, Dirk approves pretty much every reasonable change (that is not Mac or |
But this is Mac right? |
With just the command-line tools, how might one accept the Xcode license? Previously xcodebuild was used for that. |
When you install the command-line tools, it pops up a UI where you accept the license. |
As node-gyp rebuild doesn't seem to need xcodebuild, we don't need to be printing the error every time GYP is run. Refs: nodejs#1057 Refs: https://chromium-review.googlesource.com/c/492046/
As node-gyp rebuild doesn't seem to need xcodebuild, we don't need to be printing the error every time GYP is run. Refs: nodejs#1057 Refs: https://chromium-review.googlesource.com/c/492046/ Refs: nodejs#569
As node-gyp rebuild doesn't seem to need xcodebuild, we don't need to be printing the error every time GYP is run. PR-URL: nodejs#1370 Refs: nodejs#1057 Refs: https://chromium-review.googlesource.com/c/492046/ Refs: nodejs#569
As node-gyp rebuild doesn't seem to need xcodebuild, we don't need to be printing the error every time GYP is run. PR-URL: nodejs#1370 Fixes: nodejs#569 Refs: nodejs#1057 Refs: https://chromium-review.googlesource.com/c/492046/
#1370 was merged. |
I'm not sure why it closed, because of |
No it doesn't, that is just a warning which will not affect your build.
Did you look at #1370 ? The title is |
@gibfahn I am guessing the issue is that most people are using plugins that use node-gyp and do not have that control. For example, I just upgraded to Node 11.5 and trying to install node-sass and getting this error.
|
@jrock2004 I have same problem |
@jrock2004 - ran into the same problem on Node.js release lines 8 (8.15.1) and 10 (10.0.0). Release line 6 (6.9.5) worked fine. Resolution on 8 and 10 required that Xcode be fully installed and that |
Thank you @mkochco |
xcodebuild now requires full xcode and not just developer tools
I have removed all commands that use xcode build and there seems to be no issues. This also means that we don't get the error message anymore.
What is the reason we actually need to use xcodebuild?
I know that this is something that should probably be raised with gyp upstream, but I wanted to make sure that this seems reasonable first.