[MacPorts] #71051: Macports should add a global "use_xcode yes" config option

[MacPorts]

#71051: Macports should add a global "use_xcode yes" config option
--------------------------+--------------------
  Reporter:  mouse07410   |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------

Comment (by mouse07410):

 > a number of ports "bake in" the path to the SDK, and sometimes the paths
 to other things, into the installed build files.

 Is it truly necessary? It sounds to me like a sure path to troubles.



  > Over the years we have standardized on this path to the baked-in
 components being into the SDK installed with the CLTs.

 Yeah, I understand. But wouldn't using the output of {{{xcrun --show-sdk-
 path}}} be far better?




 > It is not insurmountable to find all these baked-in spots and try to
 have them overrideable at runtime to the actual SDK location . . .

 This would be the optimal solution. But I suspect it to be quite an
 effort. I don't think I have time or skills :-(  to do that, and of course
 I cannot assign others to it.



 > Much easier to just assume that the SDKs are in the location the CLTs
 have put them, and go forth from there.

 Yes, except that CLT tend to be broken much more often than Xcode itself
 (and that's quite a high bar!), and - besides Macports - some other
 toolchains (Haskell, for example) can't work with it.

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