Bouncing around a few things today.
=> More informations about this toot | More toots from thelastpsion@bitbang.social
FFS.
Also... #ASIO? That's Windows audio. Why is it being compiled in #MAME on #HaikuOS?
EDIT: Wrong ASIO! It's boost.org's asio library - thanks to @polpo for the pointer!
Thing is, this (MAME 0.266) compiled fine on Haiku R1B4. So either I've screwed up my upgrade to R1B5, or something's changed in R1B5 to break the build.
I'm getting the same error when compiling MAME 0.269, but a completely different error with MAME 0.270.
I'm annoyed, but I think these are all problems for another day.
=> View attached media | View attached media
=> More informations about this toot | More toots from thelastpsion@bitbang.social
After finding this #HaikuOS forum thread, I've got #MAME 0.266 to compile on R1B5!
https://discuss.haiku-os.org/t/porting-issues-r1b4-vs-nightly/13968
I've also switched it to using Haiku's boost asio package, rather than the one bundled with MAME.
0.269 is currently compiling with the _DEFAULT_SOURCE mod. (See screenshot of me connecting to my Haiku build box with #tmux.) I'm confident that it'll build fine.
The way I've done it might not be The Haiku Way, so I'll defer to people who know better than me when I do the pull request.
=> More informations about this toot | More toots from thelastpsion@bitbang.social
[#]MAME 0.270 is a different matter. From what I remember, it was failing right at the start of the compile job - something to do with genie. I'll have to have a look through the commits to see what's changed.
I can't work on this today (and probably not until next week at the earliest), so I might just do a pull request for 0.269 so that there's at least a later version of MAME than 0.266 in HaikuPorts.
[#]HaikuOS
=> More informations about this toot | More toots from thelastpsion@bitbang.social
[#]MAME 0.269 compiled fine on #HaikuOS, as expected.
I had a quick go at compiling MAME 0.270 in case it was an easy fix.
For some reason, the new files in the 3rdparty/genie/build/gmake.haiku folder aren't being added to the patchset by haikuporter -e mame, even though it works fine for 0.269 and earlier. The patches are detected as changes when running git status, too.
=> More informations about this toot | More toots from thelastpsion@bitbang.social
Pull request created on HaikuPorts for MAME 0.269, including the switch to Haiku's own boost asio package, the fix for asio on R1B5, and the Psion SIBO ASIC5 serial fix.
MAME 0.270 will have to wait until I can work out what's going on with those genie/gmake files not being added to the patchset.
=> More informations about this toot | More toots from thelastpsion@bitbang.social
Wanted a break from $dayjob work, so I thought I'd have one final go at #MAME 0.270 on #HaikuOS.
It feels like git commit -a isn't picking up every file it should, because manually git adding the missing files worked fine and MAME is now building!
Same thing just happened when updating the recipe for a different Haiku package (deark). I'd renamed a file, but git commit -a only picked up that a file had been "deleted", not that there was a "new" file to add. Had to quickly git --amend.
=> More informations about this toot | More toots from thelastpsion@bitbang.social
text/geminiThis content has been proxied by September (ba2dc).