[MacPorts] #41783: Always use Mac OS X SDK

[MacPorts]

#41783: Always use Mac OS X SDK
---------------------------+--------------------------------
  Reporter:  ryandesign@…  |      Owner:  macports-tickets@…
      Type:  enhancement   |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  base          |    Version:  2.2.99
Resolution:                |   Keywords:
      Port:                |
---------------------------+--------------------------------

Comment (by ryandesign@…):

 My understanding is that specifying the SDK is necessary when compiling
 for other (usually older) OS X versions (in addition to setting the
 deployment target to that OS X version), which is not a primary purpose of
 MacPorts but is nevertheless something some users want to do, and MacPorts
 has that capability, via unadvertised settings in macports.conf.

 My motivation for wanting to always use the SDK is that editing these
 unadvertised settings often leads to build failures because nobody tests
 their ports with these settings changed. Always using the SDK would expose
 those problems to everyone, thus leading to the problems being noticed and
 hopefully fixed and improving the experience for users who want to change
 these settings.

 However, in addition to the problems Mojca mentioned in comment:10 and the
 gcc problem I had in comment:7, using an SDK would require Xcode, and many
 users desire to be able to use MacPorts without Xcode, instead just using
 the command line tools. And I acknowledge that that would be nice, since
 the command line tools are tiny compared to Xcode, and users don't like to
 waste disk space, especially on an SSD. If we want to try to use SDKs
 more, then one possibility would be to only use the SDK if Xcode is
 installed, and not use it if only the command line tools are installed.

-- 
Ticket URL: <https://trac.macports.org/ticket/41783#comment:11>
MacPorts <https://www.macports.org/>
Ports system for OS X