On Jul 5, 2020, at 17:15, Jason Liu wrote:
> My guess, however, that the more likely reason upstream projects don't
> typically keep these sorts of fixes around is because they don't want it
> dirtying up their code for any longer than necessary. Even if you strip out
> the comment lines, th
On Sun, Jul 5, 2020 at 12:08 AM Fred Wright wrote:
>
> On Wed, 3 Jun 2020, Jason Liu wrote:
>
> [...]
> > A solution I found which some projects (e.g. Qemu) have implemented
> > basically replaces the new AppKit constants with the old AppKit ones
> using
> > *#define* directives if the OS version
On 2020-7-5 14:08 , Fred Wright wrote:
>
> Since having those defined differently would only be expected in cases
> where the build target is a range of OS versions, and since MacPorts has
> no concept of "OS version universality" and hence always targets one
> specific OS version, once would expe
oh, btw Fred, your impression of MAC_OS_X_VERSION_MAX_ALLOWED is not quite
right.
It doesn't indicate removed features. It indicates the SDK version you are
currently building with, so you know what API you can use.
This is always confusing, which is why we use what we do in legacysupport, in
> several messages
>
> Fred Wright fw at fwright.netÂ
> <mailto:macports-dev%40lists.macports.org?Subject=Re%3A%20several%20messages&In-Reply-To=%3Calpine.LRH.2.21.2007042035180.14781%40sh.sonic.net%3E>
> Sun Jul 5 04:08:09 UTC 2020
>
> Previous message (by th
On Wed, 3 Jun 2020, Jason Liu wrote:
[...]
A solution I found which some projects (e.g. Qemu) have implemented
basically replaces the new AppKit constants with the old AppKit ones using
*#define* directives if the OS version is below 10.12. I've created a
separate header file that gathers toget
