bslathi19/cc65
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Renamed none.lib to no-platform.lib

Browse Source
This commit is contained in:
bauen1
2018-01-02 15:15:27 +01:00
parent d9ba279e89
commit 26350714ee
2 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/customizing.sgml
View File

@@ -81,7 +81,6 @@ SEGMENTS {
ZEROPAGE: load = ZP, type = zp, define = yes; ZEROPAGE: load = ZP, type = zp, define = yes;
DATA: load = ROM, type = rw, define = yes, run = RAM; DATA: load = ROM, type = rw, define = yes, run = RAM;
BSS: load = RAM, type = bss, define = yes; BSS: load = RAM, type = bss, define = yes;
HEAP: load = RAM, type = bss, optional = yes;
STARTUP: load = ROM, type = ro; STARTUP: load = ROM, type = ro;
ONCE: load = ROM, type = ro, optional = yes; ONCE: load = ROM, type = ro, optional = yes;
CODE: load = ROM, type = ro; CODE: load = ROM, type = ro;
@@ -95,7 +94,6 @@ The meaning of each of these segments is as follows.
<p><tt> ZEROPAGE: </tt>Data in page 0, defined by ZP as starting at $0 with length $100 <p><tt> ZEROPAGE: </tt>Data in page 0, defined by ZP as starting at $0 with length $100
<p><tt> DATA: </tt>Initialized data that can be modified by the program, stored in RAM <p><tt> DATA: </tt>Initialized data that can be modified by the program, stored in RAM
<p><tt> BSS: </tt>Uninitialized data stored in RAM (used for variable storage) <p><tt> BSS: </tt>Uninitialized data stored in RAM (used for variable storage)
<p><tt> HEAP: </tt>Uninitialized C-level heap storage in RAM, optional
<p><tt> STARTUP: </tt>The program initialization code, stored in ROM <p><tt> STARTUP: </tt>The program initialization code, stored in ROM
<p><tt> ONCE: </tt>The code run once to initialize the system, stored in ROM <p><tt> ONCE: </tt>The code run once to initialize the system, stored in ROM
<p><tt> CODE: </tt>The program code, stored in ROM <p><tt> CODE: </tt>The program code, stored in ROM
@@ -304,16 +302,17 @@ also forcing a BRK instruction into the CPU.
The next step in customizing the cc65 toolset is creating a run-time The next step in customizing the cc65 toolset is creating a run-time
library for the targeted hardware. The recommended way to do this is to library for the targeted hardware. The recommended way to do this is to
modify the platform-independent standard library of the cc65 distribution. modify the platform-independent standard library of the cc65 distribution.
It is named &quot;none.lib&quot; in the lib directory of the distribution. It is named &quot;no-platform.lib&quot; in the lib directory of the
cc65 distribution.
When using &quot;none.lib&quot; we need to supply our own <tt>crt0</tt> When using &quot;no-platform.lib&quot; we need to supply our own <tt>crt0</tt>
module with custom startup code. This is simply done by first copying the module with custom startup code. This is simply done by first copying the
the library and giving it a new name, compiling the startup code with ca65, the library and giving it a new name, compiling the startup code with ca65,
and finally using the ar65 archiver to add the module to the new library. and finally using the ar65 archiver to add the module to the new library.
The steps are shown below: The steps are shown below:
<tscreen><verb> <tscreen><verb>
cp /usr/local/share/cc65/lib/none.lib sbc.lib cp /usr/local/share/cc65/lib/no-platform.lib sbc.lib
ca65 crt0.s ca65 crt0.s
ar65 a sbc.lib crt0.o ar65 a sbc.lib crt0.o
</verb></tscreen> </verb></tscreen>

2
libsrc/Makefile
View File

@@ -33,7 +33,7 @@ TARGETS = apple2 \
sim65c02 \ sim65c02 \
supervision \ supervision \
telestrat \ telestrat \
none no-platform
DRVTYPES = emd \ DRVTYPES = emd \
joy \ joy \