Chapter 9 of 9
Hand someone a disk they can run
Two people want your project. A friend wants to try it. Another programmer wants to add a seventh word. Prepare two different handoffs and test what each person gets.
Pack a six-word disk
- Start a fresh Hello Disk project in its own folder. In assets/words.txt add ORBIT on a new line after PLUS. Use uppercase letters. The supplied generator skips blank lines, accepts one A–Z word per nonblank line and requires the encoded list, including its returns and terminator, to fit in 256 bytes.
- Save, then Build Disk. Open Show Build Products and find HELLO.dsk. Copy it to a separate folder and give the copy a recognizable Mac filename such as Orbit Crew.dsk. The guest executable inside still has the name HELLO.
- Finish any pending writes and preserve open guest work. Start at OK on a fresh Disk BASIC machine. In the floppy controls, mount your copied image in FD0. This test starts from the disk you will share, independently of the C editor.
- Type DOS and press Return. Look for ORBIT beneath PLUS, followed by DISK RESULT: 0 and GENERATED WORD COUNT: 6.
- On a fresh start with that copy mounted, type LOADM"HELLO":EXEC and press Return. Look for the same three clues. This route loads the executable by name and transfers control to it.
Write those two commands on the disk label you send your friend. Typing DOS works because the generated project installs a boot helper on track 34. Project Settings → Disk & Run → DOS boot → Run this program controls that choice. The helper feeds Disk BASIC the load-and-execute command. It consumes one track of the generated floppy. The disk and the instructions are enough for a player with a compatible Disk BASIC setup.
Hand over the recipe too
For the programmer, copy the saved project folder: the Makefile, project configuration, source, headers, word list and generator. A copy of HELLO.dsk is useful for comparison. It cannot tell the new programmer where you chose the word ORBIT.
Close the project, then use Open in C Development to select the copied folder. Check its word list, select Debug, and Build Disk. Launch the result. Read the sixth word and count. This last test catches an easy packaging mistake: copying an older source folder alongside a newer floppy.
Open Build History to identify the build you just made. Check the configuration, build action and the Program or Disk indicators before using its Finder button. If you return to the project later, changed sources can make an earlier executable unsuitable for debugging. Keep the source and the tested image in your handoff folder even if you later clean out older build products.
Bring someone else's Makefile
A downloaded project may call its default target all, a program filename, or something else. Open the trusted source folder and look at its Makefile before building. In Project Settings → Build, choose Custom Makefile to keep its rules. A blank ordinary build target lets Make choose its default. Set Build Disk, the expected binary and disk names, and Disk & Run from the rules you actually find. A successful target that builds only a binary cannot supply a missing data disk.
In Libraries, a custom project can bind a Makefile directory variable to a bundled library, or append the library to a linker variable used by its link recipe. Enter the name used by that Makefile and choose a minimum version when one matters. A recipe that rebuilds a local library from its own sources needs those sources. A prepared archive satisfies a recipe that links an existing library. Check Preview for generated projects and the build output for either kind.
If you also hand the project to an assistant, open it in C Development and export a connection for that project. Custom recipes and explicitly shared support folders need local approval; the connection does not grant access to an entire checkout by implication. Keep the original Makefile in control of its build, and retain the matching debug evidence if the next developer needs verified source stops. A disposable test disk is a working result, while the source folder and recipe remain the reproducible handoff.
To see why a guest program can depend on a ROM even when every Mac tool is bundled, return to the disk reader. For an unfamiliar include or linker name, open Find a call.