[MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path

[MacPorts]

#66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for
'macosx10.11' using --show-sdk-path
-----------------------------------+---------------------------------
  Reporter:  thetrial              |      Owner:  MarcusCalhoun-Lopez
      Type:  defect                |     Status:  assigned
  Priority:  Normal                |  Milestone:
 Component:  ports                 |    Version:  2.8.0
Resolution:                        |   Keywords:  elcapitan legacy-os
      Port:  qt511-qtimageformats  |
-----------------------------------+---------------------------------

Comment (by kencu):

 Replying to [comment:31 jmroot]:
 > If you mean the change to prevent the port from failing to parse on non-
 Darwin platforms, I doubt that caused this problem.

 You do so much work to keep macports alive. Thank you for all that, if I
 have not said it often enough.

 You are of course correct in pointing out that it would be best if the
 qt5* ports obeyed MacPorts' SDK settings instead of doing their own thing.
 I have tried to do this before, and it proved difficult to both implement
 and test. There are so many qt5 versions, all different, and so many
 different system configurations to test, and the qt5 configure script is
 all written in hand-tweaked shell, that it is overwhelming to do it
 robustly across all those versions and systems.

 It is very easy to test if the last fix I pushed to the portfiles to test
 for the presence of the 10.11 SDK did or did not work. I will leave that
 as an exercise for the interested reader, if there is one. I am sorry I
 did not properly consider the non-darwin systems in so doing... my ubunutu
 macports build was broken just then, recently resuscitated.

 Marcus has a whole new approach to testing for the SDK that avoids xcrun
 completely and works. Perhaps we just throw in the towel and push that
 now, and we can move on to more important things?

 I have since fixed dozens and dozens of ports on M1 macs since I got my
 new MBPro screamer, and that is where my focus is going to be going
 forward, not back on this old headache.

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