I found Joshua Root's messages in the spam trap, so now I understand a bit more.
When you say "The difference is that the 10.14 SDK no longer allows compiling for 32-bit" does that mean that particular capabilities have been removed from the compiler, the libraries, or Xcode? -- Randolph M. Fritz On Tue, Oct 23, 2018 at 8:29 PM Randolph M. Fritz <rmfri...@gmail.com> wrote: > Thanks, everyone, for the discussion. I'll have to look into how it > applies specifically to our app. > -- > Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com > > > On Mon, Oct 22, 2018 at 8:54 PM Mark Anderson <e...@emer.net> wrote: > >> Oh yeah, I mean CodeWeavers / WineHQ - Apple doesn't care at all. I've >> been to enough WWDCs to know that. Good to know they are on it. >> >> —Mark >> _______________________ >> Mark E. Anderson <e...@emer.net> >> >> >> On Mon, Oct 22, 2018 at 12:13 AM Ryan Schmidt <ryandes...@macports.org> >> wrote: >> >>> >>> >>> On Oct 21, 2018, at 11:57, Mark Anderson wrote: >>> >>> > When I run a 32 bit command line app, I get the popup warning that >>> this “Isn’t optimized for my Mac”. >>> >>> You will get that popup when you run *any* 32-bit app. >>> >>> > It’s kind of annoying that they’re removing the possibility when >>> things like wine really need a 32bit space since Windows is no where near >>> as far along on 32->64 bit. >>> >>> Apple appears not to care. >>> >>> > I hope they’re planning to spin up hypervisor.framrwork or something >>> to fix that. >>> >>> It depends who you mean by "they". If you mean Apple, then no; they are >>> clearly moving the Mac along a path of removing 32-bit support. On the >>> other hand, CodeWeavers, one of the developers of Wine, has been working on >>> a way to continue to run 32-bit Windows apps in Wine on macOS even after >>> Apple removes the ability to run 32-bit programs. I do not know the >>> specifics of how they plan to accomplish this. >>> >>>
