Re: macOS SDK selection woes, Darwin.mk out of date

[Greg Troxel <gdt%lexort.com@localhost>]

Jonathan Perkin <jperkin%pkgsrc.org@localhost> writes:

> * On 2025-01-11 at 15:46 GMT, Greg Troxel wrote:
>
>>  #include <...> search starts here:
>>   /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1
>>   /Library/Developer/CommandLineTools/usr/lib/clang/16/include
>>   /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include
>>   /Library/Developer/CommandLineTools/usr/include
>>   /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks (framework directory)
>
> This seems wrong.  On my local system I have MacOSX15.2.sdk and it
> works ok:

thanks, will dig into what's where vs other systems.

>>Looking at mk/platform/Darwin.mk, the comments about versions stops at
>>13.  I remember there used to be a table mapping os version to sdk
>>version, but I can't find that now.  bootkstrap/README.Darwin mentions
>>OSX_SDK_MAP, but that's not in mk/platform/Darwin.mk.  I remember there
>>being more detail in README.Darwin, but perhaps it's all obsolete and
>>was gc'd.
>
> We stopped doing that, mostly because there is no such thing as a
> correct mapping between OS and SDK.  For example for my binary
> packages I build against the 12.3 SDK but on Sonoma.

Thanks, I purged the obsolete/wrong MAP stuff.

> The recommended path is to pick an SDK and stick with it.  The
> bootstrap script supports MACOSX_DEPLOYMENT_TARGET these days to help
> with that. That way you don't get screwed by Apple on arbitrary
> upgrades.

It does, but I can't figure out what to put in the variable, and trying
lots of things doesn't seem to work.  e.g., a command expanded from what
would be run

  /usr/bin/xcrun --sdk MacOSX14.5.sdk --show-sdk-path

fails to find it.  I tried with and without .sdk, and that caps matching
the dir names, and lower case.  xcrun's man page tells me to use
xcodebuild but that's not installed.  Probably one example would be
adequate.