5 | | Yes, the existence of /usr/lib/libxcselect.dylib (xcode-select) indicates macOS >= 10.9 which we assume is the earliest macOS version that moved CLT from / to /Library/Developer/CommandLineTools/. For < 10.9 we agreed that using CLT alone isn't sufficient enough so we always set use_xcode yes. |
6 | | > |
7 | | > > That would match what is done elsewhere. Using the headers in /usr/include is safer than using the SDK in Xcode because the latter could be for a newer OS version, which causes problems with build-time detection of features. |
8 | | > |
9 | | > Yeees, since Apple doesn't necessarily ship the needed SDK versions with all supported Xcode versions any longer. But also back then, using the provided SDKs was safer pre-SIP. |
10 | | > |
11 | | > |
| 5 | Yes, the existence of /usr/lib/libxcselect.dylib (xcode-select) indicates macOS >= 10.9 which we assume is the earliest macOS version that moved CLT from / to /Library/Developer/CommandLineTools/. |
| 6 | |
| 7 | For < 10.9 we agreed that using CLT alone isn't sufficient enough so we always set use_xcode yes. |