[prev in list] [next in list] [prev in thread] [next in thread]
List: wine-devel
Subject: Re: What macOS SDK is being tested against on gitlab?
From: Dean Greer <gcenx83 () gmail ! com>
Date: 2022-09-23 14:54:46
Message-ID: CAN4MNMmAJf0ZpcAN8WJp4=p57Xqa6qT39NcvK9c-hR9s+R5V5w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Alexandre,
> At this point I don't think we care about testing i386 builds for
macOS. We should soon have a way of building the 32-bit PE dlls as part
of the 64-bit build, which should be the default going forward.
Was this implementation confirmed to also work on legacy macOS versions
that still natively support 32Bit?
More of a concern is recent macOS SDKs are marking functions as
depreciated, when those get swapped out with the newer version (usually
just renamed), if the old name isn't mapped building against older SDKs
will be broken.
Keeping wine(64) buildable against MacOSX10.13.SDK would be the minimum for
comparability's sake, still being able to build against MacOSX10.11 (or
MacOSX10.10.SDK final revision) would be more ideal at least being
buildable against 10.13 would be required to still support the 32Bit wine
loader.
On Fri, Sep 23, 2022 at 10:43 AM Alexandre Julliard <julliard@winehq.org>
wrote:
> Dean Greer <gcenx83@gmail.com> writes:
>
> > Hi Alexandre,
> >
> >> Yes, it's a dedicated Mac Mini that we have setup for that purpose,
> > currently running macOS 12.5.1. I installed a number of Homebrew
> > packages that are necessary for building Wine. If there are specific
> > queries you'd like me to run on that box I'd be happy to.
> >
> > The minimum packages would be;
> >
> > # build deps
> > brew install bison \
> > pkg-config \
> > mingw-w64
> >
> > # runtime deps
> > brew install freetype \
> > gphoto2 \
> > gst-plugins-base \
> > krb5 \
> > mingw-w64 \
> > molten-vk \
> > sdl2
> >
> > # casks
> > brew install --cask xquartz
> >
> > PATH would need to be appended with $(brew --prefix krb5)/bin
> >
> > A copy of MacOSX10.13.sdk from Xcode9.3 (or later version of Xcode9)
> placed into /Library/Developer/CommandLineTools/SDKs/ then the testbot
> could also test compiling i386 wine.
> >
> > configure/make wine64 then set the following before running configure
> for i386;
> > export
> SDKROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX10.13.sdk"
> > export
> PKG_CONFIG_LIBDIR="/opt/X11/lib/pkgconfig:/opt/X11/share/pkgconfig"
> >
> > That would at least cover the basics for an i386 build without needing a
> legacy macOS runner
>
> At this point I don't think we care about testing i386 builds for
> macOS. We should soon have a way of building the 32-bit PE dlls as part
> of the 64-bit build, which should be the default going forward.
>
> --
> Alexandre Julliard
> julliard@winehq.org
>
[Attachment #5 (text/html)]
<div dir="auto">Hi Alexandre,</div><div dir="auto"><br></div><div dir="auto">> \
<span style="color:rgb(0,0,0)">At this point I don't think we care about testing \
i386 builds for</span></div><span style="border-color:rgb(0,0,0) rgb(0,0,0) \
rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)">macOS. We should soon have a way of \
building the 32-bit PE dlls as part</span><br \
style="font-family:-apple-system,HelveticaNeue"><span style="border-color:rgb(0,0,0) \
rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)">of the 64-bit build, which \
should be the default going forward.</span><div dir="auto"><br></div><div \
dir="auto">Was this implementation confirmed to also work on legacy macOS versions \
that still natively support 32Bit?</div><div dir="auto"><br></div><div \
dir="auto">More of a concern is recent macOS SDKs are marking functions as \
depreciated, when those get swapped out with the newer version (usually just \
renamed), if the old name isn't mapped building against older SDKs will be \
broken.</div><div dir="auto"><br></div><div dir="auto">Keeping wine(64) buildable \
against MacOSX10.13.SDK would be the minimum for comparability's sake, still \
being able to build against MacOSX10.11 (or MacOSX10.10.SDK final revision) would be \
more ideal at least being buildable against 10.13 would be required to still support \
the 32Bit wine loader.</div><div dir="auto"><div dir="auto"><br></div><div \
dir="auto">On Fri, Sep 23, 2022 at 10:43 AM Alexandre Julliard <<a \
href="mailto:julliard@winehq.org">julliard@winehq.org</a>> wrote:<br></div><div \
dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Dean \
Greer <<a href="mailto:gcenx83@gmail.com" \
target="_blank">gcenx83@gmail.com</a>> writes:<br> <br>
> Hi Alexandre,<br>
><br>
>> Yes, it's a dedicated Mac Mini that we have setup for that purpose,<br>
> currently running macOS 12.5.1. I installed a number of Homebrew<br>
> packages that are necessary for building Wine. If there are specific<br>
> queries you'd like me to run on that box I'd be happy to.<br>
><br>
> The minimum packages would be;<br>
><br>
> # build deps<br>
> brew install bison \<br>
> pkg-config \<br>
> mingw-w64<br>
><br>
> # runtime deps<br>
> brew install freetype \<br>
> gphoto2 \<br>
> gst-plugins-base \<br>
> krb5 \<br>
> mingw-w64 \<br>
> molten-vk \<br>
> sdl2<br>
><br>
> # casks<br>
> brew install --cask xquartz<br>
><br>
> PATH would need to be appended with $(brew --prefix krb5)/bin<br>
><br>
> A copy of MacOSX10.13.sdk from Xcode9.3 (or later version of Xcode9) placed into \
/Library/Developer/CommandLineTools/SDKs/ then the testbot could also test compiling \
i386 wine.<br> ><br>
> configure/make wine64 then set the following before running configure for \
i386;<br> > export \
SDKROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX10.13.sdk"<br> > \
export PKG_CONFIG_LIBDIR="/opt/X11/lib/pkgconfig:/opt/X11/share/pkgconfig"<br>
><br>
> That would at least cover the basics for an i386 build without needing a legacy \
macOS runner<br> <br>
At this point I don't think we care about testing i386 builds for<br>
macOS. We should soon have a way of building the 32-bit PE dlls as part<br>
of the 64-bit build, which should be the default going forward.<br>
<br>
-- <br>
Alexandre Julliard<br>
<a href="mailto:julliard@winehq.org" target="_blank">julliard@winehq.org</a><br>
</blockquote></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic