ACKitchen: write it, cook it, serve it to an Amiga.
ACKitchen is the development lab built into Cradle. You write a program, choose a compiler and a CPU, cook it on your PC in seconds, and serve the result straight into a running Amiga to try it.
We built it because we were doing the same thing hundreds of times a day for the Open family: compile on Linux, copy the file into an instance, run it, read what went wrong. Now that loop is one button, and every step leaves a record.
The Editor, as it runs today
A kitchen, on purpose.
The names are a small joke that turned out to be useful, because each one says exactly what a part does.
Compilers on your PC
Each stove is a pinned cross-compiler kept in its own folder. It is built once and never fetches anything by itself: you supply the AmigaOS NDK, and it stays on your machine.
Compilers inside an Amiga
For languages that only have a native compiler, such as Amiga E and AmiBlitz, the cook happens inside a build instance. These are planned.
Every build is a record
An order says "make me this". The finished result is a plate, with its log, its files and where they came from. Only registered recipes can run, so an order can never carry code of its own.
Three stoves today.
Pick one in the Editor, with a CPU: 68000, 68020 or 68040. The Editor tells you what each stove still needs before it can cook.
os32
GCC 6.5 for AmigaOS 3.x, with vasm and vlink, for C, C++ and 68k assembler. Everything in OpenUp has been built with it.
os32-gcc16
Our GCC 16.2 for AmigaOS 3.x, for modern C and C++23. It passed all 32 of our qualification tests on AmigaOS 3.2.
aros68k-gcc16
GCC 16.2 and binutils 2.47 for AROS on the 68k, built from GNU's own sources, for the AROS guests and the game ports.
Next: a stove for AmigaOS 4.1 on PowerPC, built the same way from GNU sources with open patches, is in progress.
What's in the kitchen.
Projects
A card per project with its languages, its files, its last cook (which stove, which CPU, and whether it worked) and the machine it was last served to. New projects start from C, 68k assembler, Amiga E or Blitz.
The Editor
Tabs, breadcrumbs, a problems gutter and the AmigaOS autodocs beside your code. Cook is Ctrl+B and Cook & Serve is Ctrl+Shift+B, straight into any running instance.
Forms
Draw a window and save it as real code: ReAction for AmigaOS 3.2 and MUI or Zune, with your own event code kept safe when you save again. It checks for things like a window with no way to close.
The Pass
Where cooked work is checked before it goes out: the orders and plates, each machine's serial port, Cradle's API and the machine's debug view in one window.
The Aminet packager
Turns a project into an Aminet upload, the .lha and its .readme, and checks Aminet's rules on names, readme fields and line lengths first. It never uploads on its own.
From a terminal
ac kitchen cook and ac kitchen serve do the same from a shell, so scripts and build machines can use the Kitchen too.
Built, and still to come.
- Orders, plates and reviews
- Three stoves, with os32 as the default
- The Editor, Forms and the Pass
- The Aminet packager
- Cooking and serving from the command line
- The Amiga E and AmiBlitz ovens
- Cooking MUI and Zune forms
- Starting a served program from Cradle
- Breakpoints and a GDB connection, so debuggers can attach
- The AmigaOS 4.1 PowerPC stove