Conversation
…h direct addressing.
|
As expected this breaks things I didn't test. Whats up with windows? |
|
From the Details it looks related to 68k |
|
The goal isn't necessarily to remove legacy code, it's to remove anything that can't be (at the very least) compile-tested on modern CI/CD. I'm not opposed to spinning up some sort of emulator in a build agent to run an older OS's compiler against this code; my feeling is that if we can't support a more collaborative development cycle for the code (i.e. if changes require a specific individual with hardware access to make dedicated time to test contributions), we can't support the code itself. Can you check whether the README or other documentation will be affected by this change? |
|
I think we're on the same page. I mean, I gave away my nice 40mhz chipped Quadra 630 when I moved 10 years ago, with the expectation that I could use Basilisk II on whatever hardware I had in the future. :) Anyone still running NetBSD on an Amiga can fork whatever old version of Basilisk II. I'm moving forward with modernization. :) Re-writing docs needs to be done, yes. |
Alright, this fork seems eager to tear out old legacy code, so lets do it. This tears out "real" 68k support.