@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!
@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!