Move libmacho-headers, dyld-headers, libunwind-headers

[mfeiri]

It turned out that some ports don’t like to find system headers in the regular include path (e.g. #39605). For this reason the xnu-headers, libc-headers, libm-headers ports have been moved to ${prefix}/Developer/SDKs/Darwin${os.major}.sdk (r117043). The other system header ports cctools-headers, dyld-headers, libunwind-headers should follow suit, but the switch needs to be synchronized with the ports that depend on these ports. At this time these are the ld64 and libcxxabi ports.

The process should be straightforward: The *-headers ports install into ${prefix}/Developer/SDKs/Darwin${os.major}.sdk and dependent ports include a "-isysroot" in the cppflags to find the headers there.

In the future we might automate this by using the “platform” variable as an indicator. The “macosx” ports would require a full Xcode SDK while “darwin” platform ports can be compiled with just the open source SDK, if it is available. We already have a comparable SDK selection feature for universal ports.

[cooljeanius (Eric Gallager)]

Cc Me!

[petrrr]

Cc Me!

[mfeiri]

I just moved the destroot of libunwind-headers to DarwinX.sdk in r127042. This might break libcxxabi and ld64 on darwin <=9, but resolves the build conflict indicated in #43869. To fix this issue, add either "-I ${destroot}${prefix}/Developer/SDKs/Darwin${os.major}.sdk/usr/include/" or "-isysroot ${destroot}${prefix}/Developer/SDKs/Darwin${os.major}.sdk --sysroot /" to the cflags on darwin <=9.

Please move the remaining cctools-headers and dyld-headers ports to DarwinX.sdk as well. As it turned out, some ports can not handle the presence of system SDK headers in regular include directories.

[larryv (Lawrence Velázquez)]

Cc Me!

[jeremyhu (Jeremy Huddleston Sequoia)]

I think that this is a bad idea. I would prefer to remove xnu-headers and libc-headers. Ports should not depend on them and should use the ones from the host.

libunwind-headers should be moved back to installing into ${prefix}/include, and we should understand why that was causing failure in other ports and fix *those* ports.

libmacho-headers similarly is fine being in ${prefix}/include. Similar to libunwind-headers, they are the headers for the MacPorts-provided libmacho port but can also be used as declarations for the base OS-provided implementation in libSystem. If they cause problems in other ports, those other ports should be fixed.

[jeremyhu (Jeremy Huddleston Sequoia)]

​https://trac.macports.org/ticket/46521 tracks removal of CarbonHeaders, libc-headers, xnu-headers, and libm-headers.

Re-purposing this bug to revert r127042 when gcc ports are fixed.

[jeremyhu (Jeremy Huddleston Sequoia)]

r131416

[jeremyhu (Jeremy Huddleston Sequoia)]

Actually, do this now because of #46521.

[mfeiri]

In the future please do not hijack tickets, turning them into their opposite. Instead close a ticket as "wontfix" and, if necessary, create a new ticket. I'll revert the summary and adjust the resolution to avoid confusion and to reflect reality.

I do not understand why you "prefer" to delete a subset of header ports instead of moving them all to a safe place. But as you have more time for macports than I do, I will not object.