Boxer
Boxer copied to clipboard
alinebee
Make Boxer 64-bit compatible for macOS 10.14
A couple of days ago, macOS 10.13.4 was released which starts issuing warnings that apps which don't support 64-bit will be retired with macOS 10.14 (expected in Autumn '18).
This means that Boxer will in its current setup stop working on the latest macOS later this year.
I get it that the main issue is that underlying DosBox is not 64-bit compatible - but at least it has been compiled with 64-bit support a couple of years ago: https://hexeract.wordpress.com/2016/09/10/building-dosbox-as-x64-binary-for-macos-sierra/
It would be great to keep Boxer running for the macOS community!
The issue isnt that it doesnt compile. Its that the dynamic core doesnt run near as efficently as it does on 32bit. Especially for more demanding games
Still hoping someone can help me in compiling @MaddTheSane's 64 bit build:
https://github.com/alunbestor/Boxer/issues/56
As I had trouble with it, I have been spending time extensively testing out 64 bit DOSBox SVN and the results are a lot better than I would have first thought. It works well enough that it appears the end of 32 bit will not entirely end my DOS gaming in macOS.
If you get frustrated waiting for Boxer to ever be updated, Dominus at VOGONS is now providing his DOSBox SVN pre-compiled for both 32 and 64 bit.
https://www.vogons.org/viewtopic.php?f=32&t=59656&p=665727#p665727
I'm working on a 64-bit build right now, based on @MaddTheSane's https://github.com/MaddTheSane/Boxer/tree/updateDosBox branch. There are a bunch of crashers and UI bugs to resolve before I'll be able to make a beta release off of it however.
@MaddTheSane's branch should compile right off the bat in Xcode 9.3; if you're getting missing header warnings then it's likely an issue with your build environment. Cleaning your build folder and/or checking out a fresh version of the branch into a new directory may cure those.
It is great to hear from you Alun and it is such good news that you are finding some time to look into updating Boxer. I should have had more faith that the cavalry would arrive! :)
Wow, after many years DOSBox 0.74-2 was just released (!!!) with 0.75 finally entering regression testing. From the release notes, there may be some changes that benefit Boxer.
To all coders working on this: Thank you very much. Your hard work is very much appreciated. Personally I lack the skills to contribute, but I hope that with DOSBOX 0.74-2 and its 64Bit support something can be done in time before macOS drops support for 32Bit applications.
I seems joysticks are an issue. I don't have any to test and verify, though: https://github.com/alunbestor/Boxer/issues/102
@alunbestor Even then, I think it'd make sense to merge the functional 64bit branch into master without making a release to have a new baseline for development since games do seem to work.
Looks like Boxer is dead for 10.15 :( really hoping for an update. Love this app!
I'm sure work will eventually continue on Boxer for 64-bit support, if someone has the skills and is willing. Until then, you could use DosBox directly and a different GUI.
@shakalaca Download Steam fresh from the site (steampowered.com) and you should get the 64-bit version installed.
The 64bit changes appear to be functional, but the code isn't released as an update, yet.
Welp - Seems like this AWESOME fellow named YOZY decided to make it work (or compiled the 64-bit branch?) on 64-bit - I tested and verified it's working in Catalina 💃
Forum I found it from: https://www.dosgameclub.com/forums/topic/boxer-app-64-bit/
File Link: https://yozy.net/files/downloads/2019/Boxer-2019-03-03.zip
Would be great to see this officially updated for Catalina 👍
Yes, just here to say thank you to the original author of Boxer, YOZY, and everyone here, for keeping Boxer around.
Seems to be this, but I can't be certain: https://github.com/alunbestor/Boxer/tree/64bit/master
@MaddTheSane, isn't your fork significantly ahead of the 64-bit master in terms of patches and improvements over the last 18 months? I have been building off your MaddsV2 branch - is that the best one to use?
I have been tempted to go back to using vanilla DOSBox, but if your branch or the master is integrated with DOSBox 74-3 and can be updated as DOSBox progresses then I would much rather stay with Boxer.
Yes, my fork uses a slightly newer version of DOSBox, but Boxer hasn't been updated to use the newer features.
@almeath Would you be willing to release what you have today as an official update?
I do not actually alter any of the code from @MaddTheSane's release. However, I understand that some people have trouble getting Boxer to build using Xcode. It is not exactly straight forward, so I do not mind linking to a pre-built copy of the maddsV2 fork (hopefully @MaddTheSane does not mind).
I will periodically update the build in this link as the code gets updated:
http://userweb.eftel.com/~almeath/mac/boxer/
Note that this is not the 64-bit 'Master' branch - this is the fork referenced above, which provides certain patches and improvements that are not currently in the master.
Also note, I build for personal use using my Apple ID, so I am not sure if this will cause problems for those running Mojave and Catalina, due to all of the notarization/code signing/quarantine flag stuff that Apple has forced upon us.
What I have done is build the Boxer app, Bundler and Standalone, using my Apple ID in Xcode. Then I manually codesign them, again using my personal Apple ID. Lastly, I manually remove any quarantine flags using "xattr -cr", as I notice that sometimes when I move apps to other Macs it falsely tells me they are damaged and should be moved to the trash. Why does Apple make things so hard these days..
Anyway, if I am breaching any terms by offering these builds someone tell me and I will remove them if necessary. Secondly, I would be interested in knowing if these actually run on Mojave and Catalina systems without causing any errors or security warnings etc.
@alunbestor
Here is the install experience downloading maddsV2 10.19.2019.zip on macOS 10.15 Catalina:
The server it's on is pretty slow:
The .zip file automatically extracts to this folder:
I think I only care about Boxer. If I double-click it, I get the error because it's not notarized:
If I right-click it and select Open, I get a similar error but with an Open button:
Once I click that I get the Accessibility Permissions dialog:
After I grant that permission, Boxer runs great:
You can Notarize the app from inside Xcode: Organizer -> Archives -> Distribute App -> Developer ID -> Upload:
BTW, if you want to notarize using the command line, there's instructions for that here — you can even notarize older already-released builds (although not sure that'll do much good since they're all 32-bit).
Thanks for testing. That seems to be the standard process for a non-notarized app in Catalina. Once you go through those initial steps it should not have to be repeated for future launches.
Going forward, there could be problems in 2020 when Apple enforces notarization, so I will look into that. However, at the moment it costs $99/year to be an Apple Developer, so it is prohibitive for a hobbyist like myself.
I will also look into a faster server, thanks for pointing that out.
Thanks very much for providing prebuilt binaries!
As far as faster servers go, perhaps just use GitHub Releases, or put the zip in GDrive or Dropbox, etc?
On a very different note, is there any actual progress on moving Boxer to 64bit?
@almeath I’d be happy to notarize it with my company’s Apple ID if that would be helpful.
On a very different note, is there any actual progress on moving Boxer to 64bit?
It depends what you mean by progress. The fork I am building from is focused on patching and fixing minor issues on what is currently an alpha release of Boxer 2, so that it is stable enough to keep using on newer versions of macOS. Being alpha software, it actually performs extremely well. @MaddTheSane's work has been very helpful in keeping Boxer going within that context. I do not think anyone other than @alunbestor would be able to add new features, especially not before an official 64 bit version is released. Hopefully, he will find the time to work on it because there is really nothing else comparable out there, in terms of ease of use and feature set. It is a great piece of software.
@almeath I’d be happy to notarize it with my company’s Apple ID if that would be helpful.
Thanks, but I think we are fine for now. I have been reading up on notarization, and there is no sign that Apple will remove the ability to run apps that have not been notarized. Maybe in a future version of macOS they might, but in Catalina you just have to follow the process you outline above, by right-clicking and selecting open.
When importing a game, it asks for and finds the intall.exe and I click next, but then gives the error "session is not ready".
Is there a work around for this?
THank you
