9fece990bea6525bec5afd8b60d1c731a4d13839
Maybe I'm naive but even after thinking about it for quite some time I can't see why it should hurt to just build the cc65 binaries from the sources "in place" and have 'make install' simply create some symlinks in usr/local/bin. The new Makfile builds the binaries with builtin search paths matching their build location. So the symlinks in usr/local/bin allow to allow to use them out-of-the-box without additional environment variables.
cc65 is a complete cross development package for 65(C)02 systems, including
a powerful macro assembler, a C compiler, linker, librarian and several
other tools.
cc65 has C and runtime library support for many of the old 6502 machines,
including
- the following Commodore machines:
VIC20
C16/C116 and Plus/4
C64
C128
CBM 510 (aka P500)
the 600/700 family
newer PET machines (not 2001).
- the Apple ][+ and successors.
- the Atari 8 bit machines.
- GEOS for the C64 and C128.
- the Nintendo Entertainment System (NES).
- the Supervision console.
- the Oric Atmos.
- the Lynx console.
The libraries are fairly portable, so creating a version for other 6502s
shouldn't be too much work.
Description
Languages
C
62.7%
Assembly
35.3%
Makefile
0.7%
PHP
0.6%
Perl
0.3%
Other
0.3%