Publish VCC Plus OSS source distribution for 3.6.2 build 60

This commit is contained in:
Brian Holman committed 2026-11-13 00:14:03 -07:00
commit c652a5276d
1192 files changed
+272368

No files matched your search

+45
View File
@@ -0,0 +1,45 @@
# Hello Disk — CMOC project example
An authored VCC Plus example under GPL-3.0-or-later, using the public-domain,
ROM-backed decbfile library included in the development runtime. No game source,
ROM, third-party standalone disk driver, generated executable, or disk image is
included in this example.
1. In VCC Plus choose **Develop → C Development → New** and select **Hello Disk — multi-file disk example** (the default). Choose a new writable folder.
2. Alternatively, copy this repository folder and **Open** it. Both approaches create your own editable source; the installed template stays unchanged.
3. **Project Settings** shows the source files, include directory, disk library,
generated resource recipe and disk launch command. Its Makefile is generated
using the same settings available in that window.
4. Boot the **Disk BASIC** machine profile. **Build** creates `HELLO.bin` and a
`HELLO.dsk` containing the executable and `WORDS.DAT`, entirely in the isolated
build workspace. It does not alter your source folder or mounted disks.
5. Use the disk launch control to mount the development disk in FD0 and run the
configured `DOS` command. You can also type `LOADM"HELLO":EXEC` at BASIC.
Confirm the media replacement when
prompted; retain any existing unsaved disk changes first.
6. The program reads its words from the emulated floppy through the Disk BASIC
ROM, prints them, then reports disk result `0` and generated word count `5`.
`main.c` calls functions in `src/display.c` and `src/disk.c`. Their shared header
is `include/hello.h`. A short Perl build recipe turns `assets/words.txt` into a C
translation unit and disk data together. Change the word list, build again and
observe the regenerated outputs. Add a breakpoint on an executable C line to
inspect the program using the existing debugger. Generated C can be inspected
from the frozen build snapshot; the editable input is the word list and recipe.
**Project Settings → Disk & Run → DOS boot** defaults to **Run this program**
for new Hello Disk copies. The build creates a small public-domain loader from
Pierre Sarrazin’s `autostart.c` under `obj/vcc-dos-boot` and reserves track 34
before adding files. It does not add a C source file to your editable project.
Choose **None** to build a disk without DOS boot. Existing project copies are
not changed automatically. Building or mounting alone does not run the program.
For command-line builds, put VCC Plus's `Contents/Resources/Toolchain/bin` on
`PATH` and run its bundled `make disk`. `make VCC_CONFIGURATION=Release disk`
uses the optimized configuration. Source changes are tracked through CMOC `.d`
header dependencies. `make clean` removes generated objects, data and disks.
Unlike the native app's isolated build, command-line Make writes these outputs
in this folder.
This example needs a functioning CoCo/Disk BASIC ROM configuration and keeps
those ROM services mapped. It is not a standalone-ROM-free disk implementation.