This is community effort to create a User Guide for the MEGA65 in the spirit of the original User Guide for the Commodore 64.
If you just want the typeset manuals, the latest pdf's from our build pipeline are available here:
(Location will be updated to files.mega65.org at a later stage when our automation permits it)
For official release increments of the documentation, hop over to the releases page at:
https://github.com/MEGA65/mega65-user-guide/releases
Use git to clone this project repo, with submodules:
git clone --recurse-submodules https://github.com/MEGA65/mega65-user-guide.gitIf you cloned another way and still need submodules (e.g. the mega65-core subfolder is empty), initialize submodules:
git submodule update --initThis project uses the LaTeX typesetting system, specifically XeLaTeX. Select and install the package appropriate for your operating system.
sudo apt install texlive)Some diagrams are implemented as SVG source files that need to be converted to EPS files for inclusion in the book. This is currently a manual step: when you update the SVG file, you must run a build command to generate the EPS files, then commit both the SVG and EPS files to the project repo.
This build step uses Inkscape v1.3.2 or later for the conversion.
brew install inkscapesudo apt-get install inkscapeCheck that Inkscape installed the inkscape command line tool and the version number is at least 1.3.2:
inkscape --versionTo regenerate the EPS files from the SVG files:
make generate-diagramsThis project uses GNU Make for coordinating build logic, and also some supplemental tools written in C. The build uses a GCC-compatible C compiler to prepare some tools. For your operating system:
build-essential packageThe User Guide project is defined using a Makefile to build.
If you are using an environment like TeXworks, do not use the built-in Build button. That is for single file building only.
For MingW32 users, use the mingw32-make command where make is indicated below. Linux and macOS users, simply use make.
make or make all will build all PDF manuals. You can also specify the name of the PDF file to build just one manual, like so:
make mega65-book.pdfThe complete list of guides that can be individually built are:
| Book | Build |
|---|---|
| User Guide | make mega65-userguide.pdf |
| Chipset Reference | make mega65-chipset-reference.pdf |
| Complete BASIC 65 Commands | make mega65-basic65-reference.pdf |
| For experimentation (don't commit) | make sandbox.pdf |
| Reference Guide | make referenceguide.pdf |
| Developer's Guide | make mega65-developer-guide.pdf |
| Guide to MEGA65 and FPGA Hardware | make hardwareguide.pdf |
| The Compendium | make mega65-book.pdf |
| As above but in CYMK for printing (Ghostscript required) | make mega65-book-cmyk.pdf |
| Documentation Style Guide | make styleguide.pdf |
Some books take several minutes to build. To make drafting easier, you can write or \include{...} new text in sandbox.tex, then either make sandbox.pdf or use a TeX IDE's build feature to test the result quickly. Move your text to the appropriate files, and revert sandbox.tex, before creating a pull request.
To delete all LaTeX-built files: make clean
To delete every generated file: make realclean
Combined with the LaTeX Workshop extension, this is a great IDE for working with the project. However be careful of the using the built-in terminal for compiling the guides. It's a powershell-based terminal and won't work with the Makefile. Nor will Command Prompt. Use a more Unix styled terminal like Git Bash.
If you wish to contribute to the MEGA65 literature, please read and follow the Documentation Style Guide. Build this document with this command:
make styleguide.pdf