6502
/
SixtyPical
mirror of https://github.com/catseye/SixtyPical.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update READMEs.

This commit is contained in:
Chris Pressey 2019-10-22 15:30:24 +01:00
parent d408e740ed
commit dc4677ade8
2 changed files with 10 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
eg/README.md
View File

@ -5,16 +5,8 @@ in subdirectories by machine architecture.
In the [rudiments](rudiments/) directory are programs which are
meant to demonstrate the elementary features of SixtyPical, and
to serve as manual integration test cases.
These sources are portable across architectures. They include
architecture-dependent libraries to produce output. Libraries
for such are provided in the `include` directory in the root
directory of the repository; make it is on the compiler's include
search path.
Some others of these sources are meant to fail and produce an error
message when compiled.
to serve as manual integration test cases. See
[the README in that directory](rudiments/README.md) for details.
### c64

16
eg/rudiments/README.md
View File

@ -2,16 +2,16 @@ This directory contains example sources which demonstrate
the rudiments of SixtyPical.
Examples that are meant to fail and produce an error message
are in the `errorful/` subdirectory.
when being compiled are in the `errorful/` subdirectory.
These files are intended to be architecture-agnostic.
For the ones that do produce output, an appropriate source
under `support/` should be included first, so that system entry
points such as `chrout` are defined. In addition, some of these
programs use "standard" support modules, so those should be included
first too. For example:
The other sources are portable across architectures. They use
`include` directives to bring in architecture-dependent libraries
to produce output. Libraries for such are provided in the
architecture-specific subdirectories of the `include` directory
in the root directory of this repository; make sure it is on the
compiler's include search path. For example:
sixtypical --run-on=x64 support/c64.60p support/stdlib.60p vector-table.60p
sixtypical --run-on=x64 -I../../include/c64/:../../include/stdlib/ vector-table.60p
`chrout` is a routine with outputs the value of the accumulator
as an ASCII character, disturbing none of the other registers,