codeblocks compiler looking in wrong directory

Is the GCC port that official C compiler for the 圆8000 that there are images of here and there?īack before I had started on my project I briefly considered doing the coding on an actual 圆8000 using that compiler, but quickly gave up on the idea as being impractical.Īs for Wine, well, I’ve never used it.

I believe you can boot the 圆8000 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. There is certainly a way to do full debugging, but it goes way above my head. I remember back in 2013 when Lydux was still doing working on his toolchain I had conversation with him about getting debugging to work. Īh, debugging my program logic can only be done on the actual 圆8000 since my project is a game, and I make heavy use of 圆8000’s excellent game specific hardware. This entry was posted in 68000, cross compiler, gcc, 圆8000 by neozeed. I’m running 10.10 so I’m not sure about older versions of OS X. So yeah it turns out you really should configure/compile gcc in a separate directory from the source. /./gcc/libgcc.mvars: No such file or directory

I ran into this fun error building GCC on OS X: On the OS X front I went ahead and built a cross compiler. And as always the keyboard will be mapped to a Japanese keyboard, so that is why the : * = keys seem in the wrong place. If you have no emulated SCSI or SASI disk, the shared directory will appear as your ‘c’ drive. You can run either the 68000 or 68030 model depending on what you like more. In the disks sub directory there is a HUMAN302 disk image which contains the needed device driver to map into the directory.

Be sure to set the shared directory under Tools -> Options to be able to map a shared directory.

Codeblocks compiler looking in wrong directory