-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build on macOS Mojave #108
Comments
I successfully build on latest Hight Sierra. |
Here is proton 3.7 dist for MacOS High Sierra. |
It looks like the SDK libraries (or at least one of them) shipped in the 10.14 SDK are no longer multi-arch and only contain x86_64 sections. You won't be able to use them to link i386 binaries. You can probably still use the 10.13 SDK under 10.14, but doing so is likely going to involve lots of fiddling with the build process. |
I found a fix! Just go to https://developer.apple.com/download/more/ then download Command Line Tools (macOS 10.14) for Xcode 10 Beta 6, install it then run build_proton.sh and it works fine! (Bit inconvenient though.) |
Tried this. Still getting the same error? Fresh install Mojave.
|
@GarethSomers can you do
|
have same error with MacOS 10.14 beta and Xcode 10 beta
iMac:proton oscar$ clang --version
|
@Luke-Nukem It's caused by an error that occurs in Mojave due to i386 architecture being deprecated. The message is:
|
@gu3st, oops, yeah I thought that was meant to be the macOS version after Mojave. |
@milomc123 thank you! I install Line Tools (macOS 10.14) for Xcode 10 Beta 6 and Line Tools (macOS 10.13) for Xcode 10 Beta 6(https://developer.apple.com/download/more/). Then I open Xcode_beta to finish the install installation. Run the build_proton.sh and it works fine. Though I don't know which file works. |
finally, failed again. ** BUILD FAILED ** The following build commands failed: |
I made a little progress on the build without installing the old commandline tools by bringing back the old sdks via https://github.com/phracker/MacOSX-SDKs w/ phracker/MacOSX-SDKs#14 and symlinking them into the Xcode 10 app bundle, much like https://github.com/devernay/xcodelegacy does, using https://github.com/kergoth/dotfiles/blob/master/osx/scripts/link-xcode-sdks, then setting flags like the command from xcodelegacy's readme:
while experimenting with the WIP makefile based buildsystem + makefile-buildsystem...kergoth:makefile-buildsystem to get it to obey the exported global flags. Still hitting other failures, but just noting it in case anyone else wants to try building with xcode 10 clt and an old macOS 10.3 SDK. |
updated to command line tools 10.14 beta 6, ran xcode select, opened x-code beta, still got:
|
Can't no longer build openal-soft as |
up? |
Failing, with the same error reported by @galiedon :
Any clue? |
@xarvh this can be solved by manually updating MoltenVK subrepo and also updating build scheme for MoltenVK to |
@yurikoles Thank you, that worked. Now the build succeeds:
However (Thank you for your patience, much appreciated). |
Tried again with a fresh clone.
This fails; digging in
|
To fix build issues on macOS, you're going to need Xcode 9 and the Xcode 9 command line tools, you can get them both at You're going to need to remove Xcode 10 from macOS to build successfully. MoltenVK and freetype2 blow up otherwise. MoltenVK is particularly problematic as it requires Xcode 9.x.x to compile successfully. freetype2 simply needs a version of gcc that can cross compile i686. First, remove Xcode 10 as you would any other application, you'll also want to purge the command line tools for Xcode 10 if you have them installed. You can purge the command line tools via Then install Xcode 9, in my instance I used Xcode 9.3. Next install the Xcode 9 command line tools, I used the version that corresponded to the full Xcode version I have installed so again, 9.3. There is one other thing that needs to be done to build successfully. meson install is used to move the compiled windows DLL files to their correct paths. The problem here is that meson detects that we're on macOS and instead looks for *.dylib files to move instead. We can fix that by modifying the script that calls this function. /usr/local/lib/python3.7/site-packages/mesonbuild/scripts/depfixer.py simply comment out the following block of code at the bottom of the script:
So it should become
Build and voila. Once you've built proton, be sure to undo the commented out lines at the bottom of depfixer as meson ordinarily needs this. In the worst case you may also need to purge and re-clone the Proton repo to remove anything you might've altered when originally trying to fix this issue. Hope this helps! |
I guess I'll just wait for a 64-bit version. 🤦🏼♂️ |
@DanielHaroldLane thanks a lot for the instructions. I did try them, but it's well beyond my ability to use a mac. =( |
macOS support has been removed: a841204 |
It was fun while it lasted. |
Trying to build on macOS Mojave 10.14 (18A371a).
Portion of
config.log
:The text was updated successfully, but these errors were encountered: