On 5/26/23 09:38, Jonathan Perkin wrote:
You can use the default MacOSX.sdk link by setting
OSX_TOLERATE_SDK_SKEW=yes, as long as you are ok with the SDK
changing from beneath you on upgrades and potentially running into
incompatibilities.
I'm not seeing a difference here. Since Darwin,mk appears to
determine the SDK path on the fly, when I update macOS from 13.2 to
13.4, then the hard-coded mapping would change from 13.1 to 13.3 along
with the symlink, correct?
OSX_SDK_MAP.13.2= 13.1
OSX_SDK_MAP.13.4= 13.3