You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, we did a simplistic check against the SDKROOT path to try
to figure out whether we should use the environment variable, or try to
find a better matching SDK instead.
This is brittle since the user might want their SDK to be in a
different place in the file system (that's kinda the whole idea of the
SDKROOT variable), and also didn't work properly with SDKs in the Xcode
Command Line Tools.
Instead, we now:
1. Parse the SDKSettings.json file under the SDKROOT, to determine
whether it is suitable for the target we're compiling for (which it
might not be when using Cargo, and targetting iOS but compiling build
scripts on macOS).
2. If it's not, attempt to find another SDK.
This allows us to give much more detailed error messages, to better
support cross-compile scenarios, and allows using parameters from the
SDK (such as the SDK version) elsewhere in the future.
0 commit comments