-
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
Calling Catalina users in @nodejs/collaborators #1936
Comments
I have upgraded to Catalina, and to my greatest surprise it did not break anything in my tool chain that I know of. I have full XCode installed at the latest version. Let me know if I need to check anything. |
I am using Catalina and |
I think the issues mostly affect people who chose to install only the CLI developer tools instead of the full Xcode. That would include me... but I am also not eager to upgrade to Catalina ATM. I'll reconsider if this lingers unresolved too long. |
No issues here either. |
Same, running Catalina just fine. |
Just did a fresh install of Catalina and https://github.com/nodejs/node-gyp/blob/master/gyp/pylib/gyp/xcode_emulation.py#L1271 returning exit status 1 was breaking my install. worked around it by just hardcoding the result in (xcodebuild -install works fine from normal user shell) |
@bdon i don't think that's catalina - i opened nodejs/node#30129 for the same issue and it looks like the python default change is the culprit there |
@codebytere Ah, you're probably right. I encountered this in the context of installing https://ports.macports.org/port/nodejs10 via MacPorts after reformatting, and I did set the global python to 3.7 instead of 2.x beforehand |
You can always revert the python default change with: |
It appears that there is no issue as long as you have XCode installed. However, I have no desire to have XCode JUST for npm and node-gyp and would prefer the tools installed without XCode. The readme instructions for Catalina work great by uninstalling and reinstalling via command line. The Mac however picks up immediately that the version being installed is out of date. If you suppress having software update then to install a latest version, there are not issues. If you allow software update to update the version then it's back to issues. |
I have the latest Catalina and latest xcode (as of the date of this comment), and I can no longer build an existing Angular app that was built in Mojava just a few months ago. When I clone the Angular app from the git repot and run 'npm install', I get node-gyp related errors:
I'm fairly new to Angular (and node for that matter), so I've been banging my head for hours on this one. |
@u84six grpc only added support for Node.js 13 in 1.24.2 (https://github.com/grpc/grpc-node/releases/tag/grpc%401.24.2) (you're using 1.23.3). |
@richardlau Yes, figured that out... the hard way. |
This issue seems to have run its course. For people coming here through search engines: see https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md |
@nodejs/collaborators: we're having an unusually high number of users showing up having problems with their build toolchain on macOS thanks to Catalina. None of us here (afaik) are using it ourselves so our ability to poke at the problem is limited. We're all pretty time-constrained too, because we have our own focuses which mostly don't include macOS specifically.
If you are using Catalina, and have a rough familiarity with the toolchain for building native addons, your help in coming up with clear and concise answers would be appreciated. You don't need to be an expert in any of the tooling, but being able to replicate problems being reported and coming up with solutions might be enough. If we have to provide documentation to improve things then we can do that, or maybe we can change the detection in GYP to improve the situation.
Here's some of the discussions happening: https://github.com/nodejs/node-gyp/issues?utf8=%E2%9C%93&q=is%3Aissue+catalina+ - the first couple mostly regard pre-releases of Catalina but they also have follow-on to Catalina GA where problems have persisted.
The most active discussion currently is #1927 but that's currently directing people to a generic macOS + Xcode CLI tools upgrade fix @ #569 (note the number of reactions in the OP). Perhaps the solutions presented there are good enough for Catalina and this is not a special case. If so, maybe we should put that into the README for macOS. Suggestions welcome!
The text was updated successfully, but these errors were encountered: