[PATCH 0/1] Cross-compiling 32-bit macOS from 64-bit-only macOS.

Dean Greer gcenx83 at gmail.com
Thu Oct 21 14:52:03 CDT 2021


> It seems to me that this should be done the same way we do it on Linux:
if we are on an x86_64 host and --enable-win64 is not specified, we add
-m32 and set host_cpu=i386. Passing --host is not required in this
configuration.

If the compile is being done via an Intel Mac that’s not required, when
compiling via an Apple Silicon Mac just launching the session via Rosetta2
will allow you to skip setting -m32 & host_cpu.

On Thu, Oct 21, 2021 at 3:35 PM Alexandre Julliard <julliard at winehq.org>
wrote:

> Brendan Shanks <bshanks at codeweavers.com> writes:
>
> > With the toolchain working, building i386 with it is now a cross-compile.
> > Apple does not prefix the commands with the host triplet though
> > (i.e. 'i386-apple-darwin'), which Wine seems to expect for
> cross-compiling.
> >
> > Specifically, configure adds "-b <host triplet>" to TARGETFLAGS, causing
> > winebuild to search for commands like ld and nm prefixed with that host
> > triplet, which fails.
> >
> > This is a patch which only sets that TARGETFLAGS when the host triplet
> > appears in $CC. I'm open to a different approach to fixing this though.
>
> It seems to me that this should be done the same way we do it on Linux:
> if we are on an x86_64 host and --enable-win64 is not specified, we add
> -m32 and set host_cpu=i386. Passing --host is not required in this
> configuration.
>
> --
> Alexandre Julliard
> julliard at winehq.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20211021/d1fb6869/attachment.htm>


More information about the wine-devel mailing list