https://bugs.winehq.org/show_bug.cgi?id=49729 Gcenx <gcenx83(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gcenx83(a)gmail.com --- Comment #1 from Gcenx <gcenx83(a)gmail.com> --- (In reply to François Gouget from comment #0)
Running the tests on macOS requires being able to run macOS in a LibVirt VM which is tricky. But just testing the macOS Wine build can be achieved in the Linux VM and is thus a much easier goal to achieve and may be enough to make sure that patches don't break the macOS build.
The following Docker containers provide a blueprint for how to set up such an environment:
* OSXCross provides the cross-compilation tools https://github.com/tpoechtrager/osxcross
* PhoenicisOrg provides an OSXCross-based container for building macOS Wine
https://github.com/PhoenicisOrg/phoenicis-winebuild/blob/master/environments... linux-amd64-wine_osxcross
Check https://github.com/kholia/OSX-KVM then combine that with macports (night also want to use my overlay https://github.com/Gcenx/macports-wine) osxcross has been very useful for building wine for macOS a larger issue is osxcross-omp (the macports package manager wrapper) needs prebuilt packages to be available but some packages are missing namely some X11 packages. If osxcross is to be used then a more stable setup would be falling back to using XQuartz 2.7.7 and building SDL2/FAudio from source but that means a lack of gstreamer1 etc -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.