I thought I’d try a 32-bit compatible installation of MacPorts today on Mojave
as a proof-of-concept, so I made a new prefix under /opt/universal and set up
macports in it.
I installed a copy of the MacOSX10.13.sdk and referenced that during the
builds.
To make it work, I made a couple of mi
On Nov 4, 2018, at 01:41, Ken Cunningham wrote:
>
> I thought I’d try a 32-bit compatible installation of MacPorts today on
> Mojave as a proof-of-concept, so I made a new prefix under /opt/universal and
> set up macports in it.
>
> I installed a copy of the MacOSX10.13.sdk and referenced that
> On 4 Nov 2018, at 1:54 pm, Ryan Schmidt wrote:
>
> On Nov 4, 2018, at 01:41, Ken Cunningham wrote:
>>
>> I thought I’d try a 32-bit compatible installation of MacPorts today on
>> Mojave as a proof-of-concept, so I made a new prefix under /opt/universal
>> and set up macports in it.
>>
>
I've just given up on 32-bit on macOS. Wine is the big pain there, but I'm
waiting for upstream to fix it since I don't use it much anyway.
I think I'm with Chris. This is a lot of effort for something that is going
to break permanently in 10.15+, we should probably just add an error to
things tha
I also think, having done it, that MacPorts in general will likely never
implement it.
Having said that, it was literally 15 minutes of tweaking portconfigure.tcl --
the rest was just build time.
Ken
> On Nov 4, 2018, at 07:04, Mark Anderson wrote:
>
> I've just given up on 32-bit on macOS.
> On Nov 4, 2018, at 6:44 AM, Christopher Jones
> wrote:
> I don’t get all the effort going into keep 32 bit going for just a little bit
> longer, until Apple completely pull the plug, in a future macOS release.
>
> Chris
>
It’s because there are a few packages, like wine and some of the e
> On Nov 4, 2018, at 5:54 AM, Ryan Schmidt wrote:
> I thought we decided we didn't want to pursue that idea, based on Joshua's
> objections, and instead we wanted to figure out a way to compile universal
> with the 10.14 SDK, maybe by making a universal 10.14 SDK,
That’s why I thought I’d ac
> On Nov 4, 2018, at 9:07 AM, Ken Cunningham
> wrote:
>
> In the end, the thing that *does* work is to set the -isysroot to
> /path/to/MacOSX10.14.sdk and the -syslibroot to /
now why would I make that typo? Need another coffee this am I guess.
In the end, the thing that *does* work is to
I think I have this clean enough to present for the curious…here are the
(minor) tweaks.
put the MacOSX10.13.sdk in the proper location in your active Xcode.app
put this in macports.conf
macosx_deployment_target 10.13
macosx_sdk_version 10.13
and in portconfigure.tcl
change l
