[MacPorts] #55441: libcxx, libcxxabi: also install into the SDKs

[MacPorts]

#55441: libcxx, libcxxabi: also install into the SDKs
--------------------------------+----------------------------------
  Reporter:  ryandesign         |      Owner:  jeremyhu
      Type:  enhancement        |     Status:  new
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:
Resolution:                     |   Keywords:  snowleopard haspatch
      Port:  libcxx, libcxxabi  |
--------------------------------+----------------------------------

Comment (by ryandesign):

 Replying to [comment:10 mojca]:
 > I'm currently using the 10.5 SDK on 10.6 in order to cross-compile TeX
 Live for 10.5 ppc & i386. I remember that at some point the binaries would
 fail to run on 10.5 otherwise (despite setting the minimum os version to
 10.5), but I didn't try to check if that's still the case. And next year
 TL will most likely require C++11, but if MacPorts installs libc++ that
 won't really help me in any way since I won't be able to distribute those
 binaries to others without MacPorts. (I didn't yet figure out whether
 shipping C++11 binaries for 10.5 users and ppc users in particular is
 actually doable.)

 If you want to continue supporting 10.5 ppc, you'll have to build the
 package for 10.5 using FSF GCC's libstdc++ for C++11 support (i.e. the
 cxx11-1.1 portgroup). There's a chance such a package would still run on
 later OS versions. But you wouldn't be using libc++. The cxx11-1.1
 portgroup is probably not currently designed to accommodate the fact that
 a different C++11 strategy might be needed on the deployment OS version
 than on the build machine OS version. The portgroup probably does not
 anticipate the user changing the deployment target at all, in fact. I
 don't know what would be involved with fixing it to do so. You could avoid
 the problem by building your distribution on a 10.5 machine.

 > Just curious: what happens if someone installs two instances of MacPorts
 on the same machine under a different prefix and then uninstalls `libcxx`
 on one of them?

 The first time the libcxx port is installed on 10.6 or earlier, it copies
 libc++ into /usr/lib. The port never deletes that copy, even if the libcxx
 port is later deactivated or uninstalled. (#49903)

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