[MacPorts] #65107: py310-pyqt5-webengine: xcrun: error: SDK "macosx10.13" cannot be located

[MacPorts]

#65107: py310-pyqt5-webengine: xcrun: error: SDK "macosx10.13" cannot be located
----------------------------------------+------------------------
  Reporter:  RivetBenoit                |      Owner:  reneeotten
      Type:  defect                     |     Status:  reopened
  Priority:  Normal                     |  Milestone:
 Component:  ports                      |    Version:  2.7.2
Resolution:                             |   Keywords:  highsierra
      Port:  py-pyqt5-webengine py-sip  |
----------------------------------------+------------------------

Comment (by kencu):

 Replying to [comment:11 mouse07410]:

 > I still think that using {{{MacOSX.sdk}}} when it's available is the
 best course on all the platforms.

 I'll try to explain why that doesn't work as well as you would hope it
 would. Please bear with me for a moment.

 Let's aay you are on MacOSX12.3. You install the latest version of Xcode,
 and it happens to come with MacOSX13.0.sdk which being the latest SDK is
 then symlinked by Apple to MacOSX.sdk. This is a very typical situation.

 So you build against MacOSX.sdk, which is MacOSX13.0.sdk. Your configure
 scripts test for things using the headers in that SDK, and this finds
 certain features in the headers as defined, certain functions are
 available, etc.

 But -- those functions are not actually in your system, which is
 MacOSX12.3. Ultimately, your build either fails to link, or if it links,
 it fails to run. You're DOA.

 Now - properly written software, which always does the right thing, has
 less of this issue. The build will actually test that things link, or
 maybe even test that they run, rather than just test to see if they are
 defined.

 Software written with Apple specifically in mind will possibly test for
 the function at runtime using one of several approaches, and use a
 fallback code path if the function is not available.

 But the vast majority of software, especially free open source software,
 is not written to that standard, and it kacks.

-- 
Ticket URL: <https://trac.macports.org/ticket/65107#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS