| 35 | |
| 36 | You can see that for some reason, the build process appears to look for the SDK location using {{{xcrun --sdk macosx}}}. In theory, that should work - but in practice it fails, as I observed with my own projects. And that command points at the {{{MacOSX11.3.sdk}}} that (as said above), symlinks to {{{MacOSX.sdk}}} (which somehow doesn't seem to work/help. |
| 37 | {{{ |
| 38 | $ xcrun --sdk macosx --show-sdk-path |
| 39 | /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk |
| 40 | }}} |
| 41 | |
| 42 | What one should do instead is drop the {{{==sdk macosx}}} argument - building on Mac won't use anything else: |
| 43 | {{{ |
| 44 | $ xcrun --show-sdk-path |
| 45 | /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk |
| 46 | }}} |
| 47 | This points at a **usable** (and current!) MacOS SDK. |