-
Notifications
You must be signed in to change notification settings - Fork 56
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
Flatpak release 1.6.19 #96
Conversation
breaks flatpak builds
Both BII and SS for macOS couldn't be built. |
BII build with xcodebuild works for me? If you're using "uae_cpu_2021" yeah I need to revise my patch for that. I'll look in to it. |
Yes, as follows.
BTW, |
Okay I managed to get a universal binary built on intel, the trick is to build gmp/mpfr with SheepShaver seemed to be failing because SDL1 was removed. I fixed that, however the build still fails for me because it can't find GTK+? I have it installed via brew. |
GTK+ is not used when building with xcodebuild.
If you can't debug with Apple Silicon, I can't merge this PR. |
Okay turns out my SheepShaver build was being messed up by having a lingering Unix/config.h from a unix build. I deleted it and I have a working SheepShaver build here. Anyone else out there with apple silicon want to help out with this? |
I now have a borrowed Apple Silicon machine, and I am happy to help out. On my Intel Mac, under Big Sur, I tried to build gmp with the
and got no error messages from
Am I doing something wrong? Is it possible that something I installed with brew is causing the problem? This is the list of my brew installs:
Again, I'll be glad to test this on Apple Silicon, but obviously I need to sort out this gmp problem first. |
You built arm64 binaries, so |
Thank you for that explanation. I've now followed the instructions and built a universal Basilisk II on an Intel Mac by building both GMP and MPFR with the ./configure command shown here, followed by May I suggest that the instructions on the main page should be clarified slightly? Instead of Also, should the instructions say to edit the schemes of the two use_cpu schemes to change Debug to Release? I've been doing this, but I don't know if it's useful Thank you again for all your work on this project! |
The subproject configuration is same as the main project regardless of individual settings, so there is no need to set it. I changed README.md description to build with |
I was also able to build with the full Xcode, but I didn't check the resulting build on an Apple Silicon Mac. If I do, I'll report back. Thank you again. |
I have M1, and have the same problem when build
|
Try |
Closing this, I have a new release in the works with significant patch reworking which obsoletes all this. |
Hi its me, the flatpak guy. :) I just released this on flathub. I rebased all my work on this repo. The summary of what I have done:
I notice there's work on JIT going on here. For stable JIT on linux you need this patch. Notably I moved the memory allocation to basilisk_glue.cpp, so that it is shared by all platforms, because that's where the RAM pointers were already. This may not be ideal and can certainly be revised.
If there's work on JIT happening I would like to be kept in the loop on that. :)
People can play with builds out of my CI if they would like. JIT works on all of them. :) However windows builds will need DLLs from MSYS2, and the macOS SheepShaver build is a "unix" build that needs sdl2/gtk+ from brew. If someone can give me an updated SheepShaver xcode project I can switch to that. :)
https://ci.appveyor.com/project/SegHaxx/macemu-flatpak