Classic Adding
jorgegv edited this page Mar 18, 2023
·
3 revisions
Please read some previous guidelines on adding new software to Classic.
Things to consider:
-
Paths:
- Under
libsrc
:- Target independent code: just in
libsrc
or subdirs of it for better organization. Example: C stubs for Classic. - Target dependent code: specific directory under
libsrc/target/<target>
. Example: target-specific versions of SP1, Arkos
- Target independent code: just in
- Under
examples
: put code in a directory with the name of the new lib or software - Under
support
: put any needed scripts, Makefiles, related to the new lib or software. Example: scripts that convert upstream Arkos sources into Z88DK Arkos sources - Under
include
: put related header files (not in directoryinclude/_DEVELOPMENT
)
- Under
-
Compiled libraries are generated under
libsrc
and installed tolib/clibs
. They are used by the compiler fromlib/clibs
. -
LST files must be adjusted (in created/modified directories and the ones above it) to take the correct paths into account.
- Overview
- Platform List
- Unsupported Platforms
- i8080/5 Support
- Homebrew hardware quickstart
- Retargetting
- Building the libraries
- Clang support
- Pragmas
- Adding to Classic
- Introduction
- Library Configuration
- CRT
- Header Files
- Assembly Language
- Library in Depth
- Embedded Platform
- Adding to NewLib
- Benchmarks
- Datatypes
- Debugging
- Decompression
- More than 64k
- Deficiencies
- Compiling Larger Applications
- Importing routines written in 8080 assembly mnemonics
- Using CP/M libraries in REL format with z88dk
- Writing optimal code
- Speeding up Compilation
- CMake usage