there is a lot of older stuff right here.

Im going to have to try their GCC, but to debug they use some binary patched SCD.X from the official C compiler it seems.

Ah, debugging my program logic can only be done on the actual x68000 since my project is a game, and I make heavy use of x68000’s excellent game specific hardware.

I remember back in 2013 when Lydux was still doing working on his toolchain I had conversation with him about getting debugging to work. There is certainly a way to do full debugging, but it goes way above my head.

I believe you can boot the x68000 up in a debugging mode or some such, and the idea was to use some sort of emulation piping to connect the executable running in the emulator with gdb running on on the build machine.

Is the GCC port that official C compiler for the x68000 that there are images of here and there?

Back before I had started on my project I briefly considered doing the coding on an actual x68000 using that compiler, but quickly gave up on the idea as being impractical.

As for Wine, well, I’ve never used it. I suppose it could be used to run the floppy image writer on a mac. But the most ideal scenario would be an automatic compile to execution in emulator build environment.

You could use wine, it’s pretty good at generic stuff like this. Also it turns out that there was an ancient GCC 1.x port to the x68000 back when it was a viable platform. I’m still trying to gather the pieces. But otherwise it’s basically printf. Debug your program logic on a machine that has a proper debugger.

The real problem is the libc, and I didn’t rely see clear way to deal with it’s missing functions.

There are a couple of things are less than ideal though. Specifically the process of going from a compiled .x file to actually running it in some emulator.

On windows there are program to edit xdd floppy images that I could use to copy executables over, and run on my emulator of choice by just booting off of the disk. Seems there is no such x68000 floppy image editor on OSX, and the shared folder trick you showcase in your post seems to be windows only.

If you have the process figured out on OSX then do share. In addition, any idea of a better way to debug programs, short of using printf?