CPCWiki - THE Amstrad CPC encyclopedia! - User contributions [en]

CPCRSlib

2018-01-23T17:40:48Z

Cpcitor: Fix broken links.

'''CPCRSlib''' is a [[:Category:C|C library]] containing routines and functions that allow to the handling of sprites and tile-mapping in Amstrad CPC.

The library is written to be used with [[Z88DK|Z88DK]] compiler or with [[SDCC|SDCC]] complier. CPCRSlib also incorporates keyboard routines to redefine and to detect keys, as well as general routines to change to the screen mode or the colours.

It can be found an explanation of each function/routine included in the library in [http://www.amstrad.es/programacion/cpcrslib.html http://www.amstrad.es/programacion/cpcrslib.html]

Last release of the library can be downloaded at:
[http://sourceforge.net/projects/cpcrslib/ sourceforge/cpcrslib]

[[CPCWYZlib|CPCWYZlib]] is included in the downloadable package of CPCRSlib. CPCWYZlib includes a music player and SFX player coded by WYZ, which can play music created with [[WYZTracker|WYZTracker]].

== Easy installation ==

If starting from scratch:

# Get [https://github.com/cpcitor/cpc-dev-tool-chain cpc-dev-tool-chain] which sets up automatically a C or ASM compiling environment on Linux, Windows, Mac.
# Create your project. In one of your C source file, just #include "cpcrslib.h".
# Compile the project. cpc-dev-tool-chain will notice the dependency and fetch and compile cpcrslib for you.

Need '''sample projects''' to see how how to start? cpc-dev-tool-chain has a cpcrslib-all target that [https://github.com/cpcitor/cpc-dev-tool-chain/blob/master/documentation/how_to_install.md#user-content-build-a-project compiles cpcrslib sample projects].

== installation ==

On Ubuntu Lucid Lynx :

<pre>
cd cpcrslib/
z80asm -v -xcpcrslib.lib @cpcrslib.lst
sudo cp cpcrslib.lib /usr/share/z88dk/lib/clibs/
sudo cp cpcrslib.h /usr/share/z88dk/include
</pre>

now it should work.

== Usage ==

A classic "Hello world" from cpcrslib :
<pre>
#include "cpcrslib.h" // CPC Library

int main(void) {
cpc_PrintStr("Hello World!");
while (!cpc_AnyKeyPressed()) { }
return 0;
}
</pre>

You should provide a zcc_opt.def in the source directory :

<pre>
DEFINE DEFINED_myzorg
defc myzorg = 16384

IF !NEED_appstartup
DEFINE NEED_appstartup
defc reqpag = 32
defc NEED_expanded = 1
ENDIF
</pre>

Compile the contents by running the compiler, pre-processor and linker in one go by typing:

<pre>
zcc +cpc -create-app -make-app -O3 -unsigned -o hello.bin hello.c -lcpcrslib -lndos -zorg=16384
</pre>

you'll have a hello.cpc file ready to be run on your CPC.

== Sources of projects using z88dk/SDCC and cpcrslib ==

*[http://espsoft.blogspot.com.es/2015/08/small-games-for-smart-minds.html Small Games for Smart Minds] by ESP Soft.
*[http://espsoft.blogspot.com.es/2015/08/mariano-dragon-capers-in-cityland.html Mariano The Dragon] by ESP Soft.
*[[Sort'em]] by LuBlu Entertainment.
*[http://cpcfreak.cpc-live.com/ Blue Angel 69] by Kevin Thacker.
*[https://cpcrulez.fr/GamesTest/nanako_descends_to_hell.htm Nanako Descends to Hell] by The Mojon Twins
*[https://cpcrulez.fr/GamesTest/nanako_in_classic_japanese_monster_castle.htm Nanako in Classic Japanese Monster Castle] by The Mojon Twins
*[https://cpcrulez.fr/GamesTest/platformer_medley_block_1.htm Mari Stormbringer Plateform Medley #1] by The Mojon Twins
*[http://www.mojontwins.com/?page_id=171 Phantomas Thales #1: Marsport] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/cheril-of-the-bosque-cpc/ Cheril of the Bosque] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/lala-prologue-cpc/ Lala Prologue] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/sir-ababol-cpc/ Sir Ababol] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/uwol-2-cpc/ Uwol 2] by The Mojon Twins.
*[http://espsoft.blogspot.com.es/2015/08/totems-columns-cpc-two.html TOTEMS: Columns CPC Two] by ESP Soft.

== See also ==

[[CPCtelera]]

[[Category:Programming]] [[Category:C]][[Category:CrossDev]]

CPCRSlib

2018-01-23T17:37:27Z

Cpcitor: Refine wording.

'''CPCRSlib''' is a [[:Category:C|C library]] containing routines and functions that allow to the handling of sprites and tile-mapping in Amstrad CPC.

The library is written to be used with [[Z88DK|Z88DK]] compiler or with [[SDCC|SDCC]] complier. CPCRSlib also incorporates keyboard routines to redefine and to detect keys, as well as general routines to change to the screen mode or the colours.

It can be found an explanation of each function/routine included in the library in [http://www.amstrad.es/programacion/cpcrslib.html http://www.amstrad.es/programacion/cpcrslib.html]

Last release of the library can be downloaded at:
[http://sourceforge.net/projects/cpcrslib/ sourceforge/cpcrslib]

[[CPCWYZlib|CPCWYZlib]] is included in the downloadable package of CPCRSlib. CPCWYZlib includes a music player and SFX player coded by WYZ, which can play music created with [[WYZTracker|WYZTracker]].

== Easy installation ==

If starting from scratch:

# Get [https://github.com/cpcitor/cpc-dev-tool-chain cpc-dev-tool-chain] which sets up automatically a C or ASM compiling environment on Linux, Windows, Mac.
# Create your project. In one of your C source file, just #include "cpcrslib.h".
# Compile the project. cpc-dev-tool-chain will notice the dependency and fetch and compile cpcrslib for you.

Need '''sample projects''' to see how how to start? cpc-dev-tool-chain has a cpcrslib-all target that [https://github.com/cpcitor/cpc-dev-tool-chain/blob/master/documentation/how_to_install.md#user-content-build-a-project compiles cpcrslib sample projects].

== installation ==

On Ubuntu Lucid Lynx :

<pre>
cd cpcrslib/
z80asm -v -xcpcrslib.lib @cpcrslib.lst
sudo cp cpcrslib.lib /usr/share/z88dk/lib/clibs/
sudo cp cpcrslib.h /usr/share/z88dk/include
</pre>

now it should work.

== Usage ==

A classic "Hello world" from cpcrslib :
<pre>
#include "cpcrslib.h" // CPC Library

int main(void) {
cpc_PrintStr("Hello World!");
while (!cpc_AnyKeyPressed()) { }
return 0;
}
</pre>

You should provide a zcc_opt.def in the source directory :

<pre>
DEFINE DEFINED_myzorg
defc myzorg = 16384

IF !NEED_appstartup
DEFINE NEED_appstartup
defc reqpag = 32
defc NEED_expanded = 1
ENDIF
</pre>

Compile the contents by running the compiler, pre-processor and linker in one go by typing:

<pre>
zcc +cpc -create-app -make-app -O3 -unsigned -o hello.bin hello.c -lcpcrslib -lndos -zorg=16384
</pre>

you'll have a hello.cpc file ready to be run on your CPC.

== Sources of projects using z88dk/SDCC and cpcrslib ==

*[http://espsoft.blogspot.com.es/2015/08/small-games-for-smart-minds.html Small Games for Smart Minds] by ESP Soft.
*[http://espsoft.blogspot.com.es/2015/08/mariano-dragon-capers-in-cityland.html Mariano The Dragon] by ESP Soft.
*[[Sort'em]] by LuBlu Entertainment.
*[http://cpcfreak.cpc-live.com/ Blue Angel 69] by Kevin Thacker.
*[http://cpcrulez.fr/zip/index.php?download=nanako-srcs Nanako Descends to Hell] by The Mojon Twins
*[http://cpcrulez.fr/zip/index.php?download=nanako2-srcs Nanako in Classic Japanese Monster Castle] by The Mojon Twins
*[http://cpcrulez.fr/zip/index.php?download=coding_src-Platformer_Medley_block_1 Mari Stormbringer Plateform Medley #1] by The Mojon Twins
*[http://www.mojontwins.com/?page_id=171 Phantomas Thales #1: Marsport] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/cheril-of-the-bosque-cpc/ Cheril of the Bosque] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/lala-prologue-cpc/ Lala Prologue] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/sir-ababol-cpc/ Sir Ababol] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/uwol-2-cpc/ Uwol 2] by The Mojon Twins.
*[http://espsoft.blogspot.com.es/2015/08/totems-columns-cpc-two.html TOTEMS: Columns CPC Two] by ESP Soft.

== See also ==

[[CPCtelera]]

[[Category:Programming]] [[Category:C]][[Category:CrossDev]]

CPCRSlib

2018-01-23T17:36:32Z

Cpcitor: Using cpcrslib with cpc-dev-tool-chain.

'''CPCRSlib''' is a [[:Category:C|C library]] containing routines and functions that allow to the handling of sprites and tile-mapping in Amstrad CPC.

The library is written to be used with [[Z88DK|Z88DK]] compiler or with [[SDCC|SDCC]] complier. CPCRSlib also incorporates keyboard routines to redefine and to detect keys, as well as general routines to change to the screen mode or the colours.

It can be found an explanation of each function/routine included in the library in [http://www.amstrad.es/programacion/cpcrslib.html http://www.amstrad.es/programacion/cpcrslib.html]

Last release of the library can be downloaded at:
[http://sourceforge.net/projects/cpcrslib/ sourceforge/cpcrslib]

[[CPCWYZlib|CPCWYZlib]] is included in the downloadable package of CPCRSlib. CPCWYZlib includes a music player and SFX player coded by WYZ, which can play music created with [[WYZTracker|WYZTracker]].

== Easy installation ==

# Let [https://github.com/cpcitor/cpc-dev-tool-chain cpc-dev-tool-chain] sets up automatically a C or ASM compiling environment on Linux, Windows, Mac.
# In one of your C source file, just #include "cpcrslib.h".
# Compile the project. cpc-dev-tool-chain will notice the dependency and fetch and compile cpcrslib for you.

Need '''sample projects''' to see how how to start? cpc-dev-tool-chain has a cpcrslib-all target that [https://github.com/cpcitor/cpc-dev-tool-chain/blob/master/documentation/how_to_install.md#user-content-build-a-project compiles cpcrslib sample projects].

== installation ==

On Ubuntu Lucid Lynx :

<pre>
cd cpcrslib/
z80asm -v -xcpcrslib.lib @cpcrslib.lst
sudo cp cpcrslib.lib /usr/share/z88dk/lib/clibs/
sudo cp cpcrslib.h /usr/share/z88dk/include
</pre>

now it should work.

== Usage ==

A classic "Hello world" from cpcrslib :
<pre>
#include "cpcrslib.h" // CPC Library

int main(void) {
cpc_PrintStr("Hello World!");
while (!cpc_AnyKeyPressed()) { }
return 0;
}
</pre>

You should provide a zcc_opt.def in the source directory :

<pre>
DEFINE DEFINED_myzorg
defc myzorg = 16384

IF !NEED_appstartup
DEFINE NEED_appstartup
defc reqpag = 32
defc NEED_expanded = 1
ENDIF
</pre>

Compile the contents by running the compiler, pre-processor and linker in one go by typing:

<pre>
zcc +cpc -create-app -make-app -O3 -unsigned -o hello.bin hello.c -lcpcrslib -lndos -zorg=16384
</pre>

you'll have a hello.cpc file ready to be run on your CPC.

== Sources of projects using z88dk/SDCC and cpcrslib ==

*[http://espsoft.blogspot.com.es/2015/08/small-games-for-smart-minds.html Small Games for Smart Minds] by ESP Soft.
*[http://espsoft.blogspot.com.es/2015/08/mariano-dragon-capers-in-cityland.html Mariano The Dragon] by ESP Soft.
*[[Sort'em]] by LuBlu Entertainment.
*[http://cpcfreak.cpc-live.com/ Blue Angel 69] by Kevin Thacker.
*[http://cpcrulez.fr/zip/index.php?download=nanako-srcs Nanako Descends to Hell] by The Mojon Twins
*[http://cpcrulez.fr/zip/index.php?download=nanako2-srcs Nanako in Classic Japanese Monster Castle] by The Mojon Twins
*[http://cpcrulez.fr/zip/index.php?download=coding_src-Platformer_Medley_block_1 Mari Stormbringer Plateform Medley #1] by The Mojon Twins
*[http://www.mojontwins.com/?page_id=171 Phantomas Thales #1: Marsport] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/cheril-of-the-bosque-cpc/ Cheril of the Bosque] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/lala-prologue-cpc/ Lala Prologue] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/sir-ababol-cpc/ Sir Ababol] by The Mojon Twins.
*[http://www.mojontwins.com/juegos_mojonos/uwol-2-cpc/ Uwol 2] by The Mojon Twins.
*[http://espsoft.blogspot.com.es/2015/08/totems-columns-cpc-two.html TOTEMS: Columns CPC Two] by ESP Soft.

== See also ==

[[CPCtelera]]

[[Category:Programming]] [[Category:C]][[Category:CrossDev]]

RSX

2018-01-20T18:10:32Z

Cpcitor: Reference documentation to write a RSX is supplied in Soft968: CPC 464/664/6128 Firmware section 10.

== Introduction ==

RSX (Resident System eXtensions) were a way to extend the command set of Locomotive BASIC, e.g. for accessing external peripherals like disk drives, light pens, speech synthesizers and so on.

RSX commands can be distinguished from normal commands by the preceding pipe symbol "'''|'''" (also called "RSX bar", "RSX pipe" or "RSX slash").

Some of the best known RSX commands are the ones provided by AMSDOS, as they were present on all CPC664, CPC6128, CPC6128+ and CPC464 with DDI-1:

'''|A''' 
Makes drive A: the current work drive

'''|B''' 
Makes drive B: the current work drive

'''|CPM''' 
Starts CP/M (or other systems) from a system disk

'''|DISC''' 
Switches back to disk drive use after |TAPE

'''|TAPE''' 
Makes the CPC use the tape recorder for file access

For a full command reference to the AMSDOS RSX commands, see [[AMSDOS]].

RSX command extensions can be implemented through ROMs (like AMSDOS or other disk operating systems) or by programs.

== Reference documentation ==

Reference documentation to write a RSX (assembly-level calls to register one, etc) is supplied in [[Soft968: CPC 464/664/6128 Firmware]] section 10.

[[Category:Stub]] [[Category:Disc Operating_System]]
[[Category:Programming]]
[[Category:BASIC| ]]
[[Category:Operating System| ]]
[[Category:Software]]
[[Category:Programming software| ]]
[[Category:Expansion ROM| ]]

Gfx2crtc

2017-11-23T16:45:37Z

Cpcitor: Describe and provide links to source.

== gfx2crtc ==

=== Introduction ===

From https://github.com/cpcsdk/gfx2crtc :

gfx2crtc - gfx convert tools to amstrad cpc format

gfx2crtc is a tool to convert gfx (linear raw 8bits per pixel or PNG 1,2 or 4 bits) in a compatible format for Amstrad CPC and Plus.

Initial Software written by : CloudStrife/Shinra (Quentin Carlier) cloudstrife@cpcscene.com.

It is spread under the CeCILL Free Software License v2, see LICENSE for more information.

See AUTHORS for the list of contributors.

=== Comparison with other tools ===

* [[ConvImgCPC]] is intended for manual tweaking and saving to CPC format with a manual workflow.
* On the contrary, gfx2crtc is perfect for automated build workflow: work on your images in some general use format like PNG, and only convert automatically at build time.
* can convert not only full screens, but also sprites (one sprite per input image, not too big)

== Platforms ==

Written in portable C. Linux, Mac OS, Windows (code mentions mingw), probably others.

== External links ==

Project used to be on https://code.google.com/archive/p/cpcsdk/downloads now removed.

* [https://github.com/cpcsdk/gfx2crtc Source code on Github: cpcsdk/gfx2crtc: Convert pictures to CPC screen format, from the command line.]
* [https://cpcrulez.fr/emulateurs_UTIL-GRA-gfx2crtc.htm gfx2crtc on cpcrulez] mostly text description, no link or source code but links to descriptions of other programs.

[[Category:Emulation Tools]]

ConvImgCPC

2017-11-23T16:18:51Z

Cpcitor: gfx2crtc portable tool intended for automated builds

[[Image:Convimgcpc.gif|thumb|ConvImgCpc]]

ConvImgCPC is a small program developped by Demoniak; it allows the conversion of PC images to the CPC.

It will read images in BMP, GIF, JPEG format and of course SCR (the format of [[The Advanced OCP Art Studio|OCP ART STUDIO]] pictures).

For SCR the files must have an [[AMSDOS]] header.

Once the image is read, it is possible to carry out some adjustments on:
* the position of the image,
* the size of the image,
* the intensity of each component R, G, B (useful for adjusting brightness of image).

Then the conversion can be made in the 3 screen modes of the CPC :
* MODE 0: 160 X 200 points with 16 possible colors from 27,
* MODE 1: 320 X 200 points with 4 possible colors from 27,
* MODE 2: 640 X 200 points with 2 possible colors from 27.
* MODE 3: a special mode wich let you use more than 4 colors in 320 x200 points.

Several modes of dithering are possible for "recreating" the missing colors.

The colors calculated by the program can be modified manually and "locked", i.e. that they will not be modified by the program during a conversion.

ConvImgCPC has an option to use the 4096 colors of the CPC+.

It is also possible to use non standard resolution (up to 736 x 272 points in mode 2)

You can edit the picture generated inside ConvImgCPC.

The image is saved to SCR format for standard formats, and when you save you can choose if the file is compressed or not.
The colors can also be saved to a seperate PAL file.

The software also makes it possible to read the palette from another file.

You can save your calculated image under an assembler source file (filled with DEFBs) so that you can include it into your programs.

You can find it here : [http://amstrad.cpc.free.fr Amstradeus]

In the download section : [http://amstrad.cpc.free.fr/download.php Download]

== Similar tools ==

* [[gfx2crtc]] portable tool intended for automated builds

[[Category:Emulation Tools]]

Dsktools

2017-11-17T08:55:40Z

Cpcitor: mention intermediate location Berlios

dsktools is a set of tools for reading and writing [[DSK]] and [[EDSK]] images to real floppy disks for use with the Amstrad/Schneider CPC range of homecomputers. The main target platform for dsktools is GNU/Linux. dsktools is written by [[Nurgle|Andreas Micklei]].

== Web links ==

* [https://github.com/cpcitor/dsktools GitHub - cpcitor/dsktools: Linux tools to read/write Amstrad CPC disk images to real floppy disks.] migrated from Berlios with source code revision history
* [http://sourceforge.net/projects/dsktools.berlios/ dsktools] (original location from before Berlios, old version 2.3)

[[Category:Emulation Tools]][[Category:CrossDev]]

Dsktools

2017-11-17T08:54:34Z

Cpcitor: Link to migrated project.

dsktools is a set of tools for reading and writing [[DSK]] and [[EDSK]] images to real floppy disks for use with the Amstrad/Schneider CPC range of homecomputers. The main target platform for dsktools is GNU/Linux. dsktools is written by [[Nurgle|Andreas Micklei]].

== Web links ==

* [https://github.com/cpcitor/dsktools GitHub - cpcitor/dsktools: Linux tools to read/write Amstrad CPC disk images to real floppy disks.] migrated project with source code revision history
* [http://sourceforge.net/projects/dsktools.berlios/ dsktools] (original location, old version 2.3)

[[Category:Emulation Tools]][[Category:CrossDev]]

Programming:Cross Development

2017-11-17T08:25:05Z

Cpcitor: Where cpcdiskxp is mentioned (Windows-specific), mention dsktools (Linux) too.

= Introduction =

Cross development is a development method where you use another machine (the host) to develop programs for the CPC (target). This is interesting because you can make a big program which sourcecode does not even fit on the CPC ram.

The main drawback is that transferring the compiled code to the CPC can be quite difficult. But there are pretty good emulators which you can use for testing.

Once you have your binary file you have two choices depending on if the game will be for [[Datacorder|cassette]] or [[Disk drives|disc]].

*[[Atari|Atari ST]] was a common 16 bit computer actually used in cross development of games on CPC.

Of course nowadays cross development use far more powerful modern computers.

*[[ZX Spectrum]] was also a source of cross development...er... let's better say [[Speccy Port|Gross Development]] indeed.

= Tools needed for cross development =

== Integrated toolchains ==

An integrated cross-development toolchain is a time saver for development as it automates all necessary steps from a full set of source materials (source code, graphics, music, parameters in whatever format is practical for editing, etc) to one or several formats ready to run on the target machines. It also sometimes includes automatically launching or notifying an emulator or target device. See e.g. [http://en.wikipedia.org/wiki/Build_automation#Advantages Build Automation on wikipedia].

Such a design has several advantage:
* allows the usage of any text/graphic editor of modern platforms
* you can change anything in one or more source files and you get an updated build quickly without error-prone manual steps
* allows arbitrary transform or generation of intermediary files (code or data).
* makes easy to have specific builds (e.g. for automated tests like to check if a different compiler produces correct code, variant build for slightly different targets)
* since most material are text files or small independent files, it benefits hugely from modern tools for revision control like [http://en.wikipedia.org/wiki/Git_%28software%29 Git] which makes sharing and merging code between developers much easier, increasing the time saved.

An ideal toolchain does not force its user into specific ways of doing things but is flexible enough to let the user adjust for whatever specific needs (use different languages, compilers, linkers, etc). Along with a properly designed and structured source tree, this makes projects less dependent on specific tools used to build them, and be more resilient to [http://en.wikipedia.org/wiki/Bit_rot bit rot] due to [http://en.wikipedia.org/wiki/Software_rot#Environment_change software build environment change].

Please note that an integrated toolchain has little to do with anything visible on-screen. A good toolchain can be triggered by most flexible enough graphical environments and generally produces a text log of the work done. Nevertheless, the concept of toolchains is more natural to Linux/Unix way of thinking/doing things, and those environments are already full of reusable and combinable tools that ease the creation and maintenance of a toolchain. Windows users can generally use tools developed for Unix through the cygwin software adaptation layer but running a Linux distribution in a virtual machine may be more practical.

There are some attempts at creating toolchains targeting the CPC.

Active as of 2017-11:

* '''[[CPCtelera]]''' integrates an out-of-the-box preconfigured build system, along with a game development library and tools. It is also multiplatform, working on Linux, OSX and Windows.
* [https://github.com/cpcitor/cpc-dev-tool-chain cpc-dev-tool-chain] integrated C or ASM development toolchain for the Amstrad CPC platform (or emulator). Includes compiler, assembler, makefile-based projects, interface between C and firmware. Designed for quick start on Linux (or similar) systems : get a copy, run "make" and get a DSK ready to run into the emulator. It even downloads and compiles tools (the cross-compiler, iDSK) if needed. Made for Linux, also works with Windows (via cygwin or similar), and probably Mac OS X. Most project+build-oriented features claims by CPCTelera comes from cpc-dev-tool-chain.
* Not an integrated toolchain, but a collection of tools that can be strung together to make one, including a DockerFile. Mentioned on [http://www.cpcwiki.eu/forum/off-topic/cpc-sdk-for-linuxunix/ CPC SDK for Linux/Unix]. Appears to have moved to https://github.com/cpcsdk

* 2012-11-12 [http://www.cpcwiki.eu/forum/programming/recommended-linux-cross-dev-tool-chain/ Recommended Linux cross-dev tool chain?] mentions a makefile-based toolchain targeting dsk images or tapes
* 2009-06-16 [http://www.cpcwiki.eu/forum/emulators/my-new-cross-development-kit/new/#new My new cross-development kit] explain what is basically a toolchain but link is broken as of 2013-01-08

== Linux ==

=== Cartridge management ===
* [[buildcpr]] [http://www.cepece.info/amstrad/download/buildcpr.zip]

=== Cross assemblers ===

* [[SjasmPlus]]
* [[Sjasm|sjasm]]
* [[Zasm]] [http://sourceforge.net/projects/zasm]
* [[ZMac]]
* GNU Binutils for z80 (z80-unknown-coff platform)
* [[Z80asm]] [http://savannah.nongnu.org/projects/z80asm]
* [[pasmo]]
* [[naken_asm]] [https://www.mikekohn.net/micro/naken_asm.php]

=== Cross compilers ===
* [[ZXBasic]]

=== Crunching ===
* [[Exomizer]]
* [[pucrunch]] [http://tj.gpa.free.fr/zip/sources/pucrunch.zip]

=== Disassemblers ===
* [[dzasm]] [http://www.cepece.info/amstrad/download/dzasm.zip]

=== Disc management ===

* [[CPCTools]]
* [[iDSK]]
* [[cpcfs]] / [[cpcxfs]]
* [[dsktools]]
* [[cpmtools 2]] [http://www.moria.de/~michael/cpmtools/]

=== Editing ===

* scite
* pico
* xemacs
* [[How to use VIM for CrossDev|Vim]]
* pluma
* gedit

=== Emulators ===
* [[Arnold (Emulator)|Arnold]]
* [[Caprice]] [http://sourceforge.net/projects/caprice32/]
* [[cpcemu]] [http://www.cpc-emu.org/]
* [[xcpc]] [http://xcpc.sourceforge.net/]

=== Tape management ===

* [[2cdt]] new version: [http://cpctech.cpc-live.com/download/2cdt.zip] — old version: [http://www.cepece.info/amstrad/download/2cdt.zip]
* [[cdtcheck]] [http://www.cepece.info/amstrad/download/cdtcheck.zip]
* [[cdttst]] [http://www.cepece.info/amstrad/download/cdttst.zip]
* [[samp2]] [http://www.cepece.info/amstrad/download/samp2.zip]
* [[UberCassette]] [http://www.retroreview.com/iang/UberCassette/]

=== Toolkits ===
* [[CPCSDK]] toolkit which contains useful tools for cross-development under Linux - [http://code.google.com/p/cpcsdk/]

=== Useful scripts ===
==== Suppress header information of a file ====
<pre>
cat file_with_header | tail -c+129 > file_without_header
</pre>

=== Needed Tools ===
These tools have to not require a lot of requirement and most of them must work in command line without GUI. This will allow
to use them with Makefile scripts. They have to be fast too, it will be disappointing to wait more when doing CrossDev than when doing code on a real CPC.
A good thing (like most of CPCTools) is to have a portable code which compile on most platforms.

* a good emulator which can be integrated in other tools. (Ramlaid first try to change Caprice is a good start)
* an integration of Ramlaid's tools with Nautilus
* ameliorations of Caprice in order to have similar functionalities than WinApe (disasm, asm, ...)
* debug the libdsk which seems to work very bad on actual computers (writting fail a lot)
* a lot of macros, or libraries for SJASMPlus shared by people in order to share code
* share a generic Makefile able to be use for build CPC project
* a lot of little command line utilities (could be add to CPCTools ?) really well done :
** graphics tools :
*** convert images from PC to CPC, or CPC to PC (cf. tools based on ImageMagick or GD)
*** equivalent of Anoine's FontCatcher
** 2 tools which work with BASIC :
*** one for create BASIC AMSDOS files from ASCII or UTF-8 text files
*** one for create ASCII or UTF-8 text files from BASIC AMSDOS files
*** (this can already be done with manageDSK for files inside a DSK, maybe extract the code from there)
** data manipulation tools :
*** ability to arrange data files for example modify bytes order in a picture file by using Gray code capabilities for changing line with modifying 1 bit

== Windows ==

=== Cross Assemblers ===

*[[Tasm|tasm]]
*[[Pasmo|Pasmo]]
*[[ZMac|ZMac]]
*[http://little-bat.de/prog/ zasm]
*[[WinApe|WinApe]]'s built in assembler
* [[naken_asm]] [https://www.mikekohn.net/micro/naken_asm.php]

=== Cross compilers (C) ===

For tutorial, see http://www.cpcmania.com/Docs/Programming/Programming.htm by Mochilote

* [[Z88DK]]
* [[SDCC]], notably [[SDCC and CPC]] had hints and practical examples about the principles of writing in C for CPC.
* [[PhrozenC]]

=== Cross compilers (Java) ===

WIP

* [[JavaGrinder]]

=== Graphics ===

*[[AMSprite|AMSprite]] - Sprite/Loading Screen Editor and graphics conversion tools

=== Sound ===

*[[WYZTracker|WYZTracker]] - Music tracker / Sound effects editor
*[[Vortex Tracker]]

== Testing on a real CPC ==

=== For cassette ===

* 2CDT to add the files to a Cassette Image File (CDT)
* Tape2WAV to convert the Cassette Image file (CDT) into a WAV file.
* Then you can run the program on the emulator the same way as you would run it on a real CPC, or
* Connect your CPC (CPC664 and CPC6128 have a cassette input) to the Line-Out output of your PC soundcard
* On the CPC type:

|TAPE:RUN"

* Start your WAV player
* Set the volume to maximum
* play the WAV file
* Wait for the program to load...

=== For disc ===

* Use CPCFS or CPCXFS to put the binary files into a Disk Image file (DSK)
* Then you can run the program on the emulator the same way as you would run it on a real CPC

If your CPC has a 3.5" disc drive then the easiest method is to transfer the DSK to a 3.5" disc using a PC with a 3.5" drive (internal, not USB).

* Then write the DSK to a 3.5" disc drive, using dsktools (Linux) or CPCDiskXP (Windows).
* Put the disc into your CPC's 3.5" disc drive and type - |B: RUN "<gamename>

== Snapshots ==

The fastest way of testing your code on an emulator is by creating a snapshot. Use [[CPCSnapshot]] to insert your assembled code into a snapshot file. Then just load the snapshot file into the emulator. Windows users may also try WinAPE's integrated assembler which assembles the code directly into the emulated CPC's memory.

== Web links ==

* [http://ramlaid.free.fr/Amstrad/English/crossDev.htm CPC Cross Development tools by Ramlaid] (Link broken as 2012-01-08. If you can help, please update.)

[[Category:Programming]] [[Category:CrossDev]]

User:Cpcitor

2017-11-12T20:56:30Z

Cpcitor: Changed name from FindYWay to cpcitor

Had a CPC since 1985, currently software dev professional, including embedded systems.

Opened a CPCWiki account on 2013-01-8 as FindYWay (no longer used), then changed name to cpcitor on forum then on CPCWiki.

Programming:Cross Development

2017-11-12T20:53:02Z

Cpcitor: Updated cpc-dev-tool-chain description.

= Introduction =

Cross development is a development method where you use another machine (the host) to develop programs for the CPC (target). This is interesting because you can make a big program which sourcecode does not even fit on the CPC ram.

The main drawback is that transferring the compiled code to the CPC can be quite difficult. But there are pretty good emulators which you can use for testing.

Once you have your binary file you have two choices depending on if the game will be for [[Datacorder|cassette]] or [[Disk drives|disc]].

*[[Atari|Atari ST]] was a common 16 bit computer actually used in cross development of games on CPC.

Of course nowadays cross development use far more powerful modern computers.

*[[ZX Spectrum]] was also a source of cross development...er... let's better say [[Speccy Port|Gross Development]] indeed.

= Tools needed for cross development =

== Integrated toolchains ==

An integrated cross-development toolchain is a time saver for development as it automates all necessary steps from a full set of source materials (source code, graphics, music, parameters in whatever format is practical for editing, etc) to one or several formats ready to run on the target machines. It also sometimes includes automatically launching or notifying an emulator or target device. See e.g. [http://en.wikipedia.org/wiki/Build_automation#Advantages Build Automation on wikipedia].

Such a design has several advantage:
* allows the usage of any text/graphic editor of modern platforms
* you can change anything in one or more source files and you get an updated build quickly without error-prone manual steps
* allows arbitrary transform or generation of intermediary files (code or data).
* makes easy to have specific builds (e.g. for automated tests like to check if a different compiler produces correct code, variant build for slightly different targets)
* since most material are text files or small independent files, it benefits hugely from modern tools for revision control like [http://en.wikipedia.org/wiki/Git_%28software%29 Git] which makes sharing and merging code between developers much easier, increasing the time saved.

An ideal toolchain does not force its user into specific ways of doing things but is flexible enough to let the user adjust for whatever specific needs (use different languages, compilers, linkers, etc). Along with a properly designed and structured source tree, this makes projects less dependent on specific tools used to build them, and be more resilient to [http://en.wikipedia.org/wiki/Bit_rot bit rot] due to [http://en.wikipedia.org/wiki/Software_rot#Environment_change software build environment change].

Please note that an integrated toolchain has little to do with anything visible on-screen. A good toolchain can be triggered by most flexible enough graphical environments and generally produces a text log of the work done. Nevertheless, the concept of toolchains is more natural to Linux/Unix way of thinking/doing things, and those environments are already full of reusable and combinable tools that ease the creation and maintenance of a toolchain. Windows users can generally use tools developed for Unix through the cygwin software adaptation layer but running a Linux distribution in a virtual machine may be more practical.

There are some attempts at creating toolchains targeting the CPC.

Active as of 2017-11:

* '''[[CPCtelera]]''' integrates an out-of-the-box preconfigured build system, along with a game development library and tools. It is also multiplatform, working on Linux, OSX and Windows.
* [https://github.com/cpcitor/cpc-dev-tool-chain cpc-dev-tool-chain] integrated C or ASM development toolchain for the Amstrad CPC platform (or emulator). Includes compiler, assembler, makefile-based projects, interface between C and firmware. Designed for quick start on Linux (or similar) systems : get a copy, run "make" and get a DSK ready to run into the emulator. It even downloads and compiles tools (the cross-compiler, iDSK) if needed. Made for Linux, also works with Windows (via cygwin or similar), and probably Mac OS X. Most project+build-oriented features claims by CPCTelera comes from cpc-dev-tool-chain.
* Not an integrated toolchain, but a collection of tools that can be strung together to make one, including a DockerFile. Mentioned on [http://www.cpcwiki.eu/forum/off-topic/cpc-sdk-for-linuxunix/ CPC SDK for Linux/Unix]. Appears to have moved to https://github.com/cpcsdk

* 2012-11-12 [http://www.cpcwiki.eu/forum/programming/recommended-linux-cross-dev-tool-chain/ Recommended Linux cross-dev tool chain?] mentions a makefile-based toolchain targeting dsk images or tapes
* 2009-06-16 [http://www.cpcwiki.eu/forum/emulators/my-new-cross-development-kit/new/#new My new cross-development kit] explain what is basically a toolchain but link is broken as of 2013-01-08

== Linux ==

=== Cartridge management ===
* [[buildcpr]] [http://www.cepece.info/amstrad/download/buildcpr.zip]

=== Cross assemblers ===

* [[SjasmPlus]]
* [[Sjasm|sjasm]]
* [[Zasm]] [http://sourceforge.net/projects/zasm]
* [[ZMac]]
* GNU Binutils for z80 (z80-unknown-coff platform)
* [[Z80asm]] [http://savannah.nongnu.org/projects/z80asm]
* [[pasmo]]
* [[naken_asm]] [https://www.mikekohn.net/micro/naken_asm.php]

=== Cross compilers ===
* [[ZXBasic]]

=== Crunching ===
* [[Exomizer]]
* [[pucrunch]] [http://tj.gpa.free.fr/zip/sources/pucrunch.zip]

=== Disassemblers ===
* [[dzasm]] [http://www.cepece.info/amstrad/download/dzasm.zip]

=== Disc management ===

* [[CPCTools]]
* [[iDSK]]
* [[cpcfs]] / [[cpcxfs]]
* [[dsktools]]
* [[cpmtools 2]] [http://www.moria.de/~michael/cpmtools/]

=== Editing ===

* scite
* pico
* xemacs
* [[How to use VIM for CrossDev|Vim]]
* pluma
* gedit

=== Emulators ===
* [[Arnold (Emulator)|Arnold]]
* [[Caprice]] [http://sourceforge.net/projects/caprice32/]
* [[cpcemu]] [http://www.cpc-emu.org/]
* [[xcpc]] [http://xcpc.sourceforge.net/]

=== Tape management ===

* [[2cdt]] new version: [http://cpctech.cpc-live.com/download/2cdt.zip] — old version: [http://www.cepece.info/amstrad/download/2cdt.zip]
* [[cdtcheck]] [http://www.cepece.info/amstrad/download/cdtcheck.zip]
* [[cdttst]] [http://www.cepece.info/amstrad/download/cdttst.zip]
* [[samp2]] [http://www.cepece.info/amstrad/download/samp2.zip]
* [[UberCassette]] [http://www.retroreview.com/iang/UberCassette/]

=== Toolkits ===
* [[CPCSDK]] toolkit which contains useful tools for cross-development under Linux - [http://code.google.com/p/cpcsdk/]

=== Useful scripts ===
==== Suppress header information of a file ====
<pre>
cat file_with_header | tail -c+129 > file_without_header
</pre>

=== Needed Tools ===
These tools have to not require a lot of requirement and most of them must work in command line without GUI. This will allow
to use them with Makefile scripts. They have to be fast too, it will be disappointing to wait more when doing CrossDev than when doing code on a real CPC.
A good thing (like most of CPCTools) is to have a portable code which compile on most platforms.

* a good emulator which can be integrated in other tools. (Ramlaid first try to change Caprice is a good start)
* an integration of Ramlaid's tools with Nautilus
* ameliorations of Caprice in order to have similar functionalities than WinApe (disasm, asm, ...)
* debug the libdsk which seems to work very bad on actual computers (writting fail a lot)
* a lot of macros, or libraries for SJASMPlus shared by people in order to share code
* share a generic Makefile able to be use for build CPC project
* a lot of little command line utilities (could be add to CPCTools ?) really well done :
** graphics tools :
*** convert images from PC to CPC, or CPC to PC (cf. tools based on ImageMagick or GD)
*** equivalent of Anoine's FontCatcher
** 2 tools which work with BASIC :
*** one for create BASIC AMSDOS files from ASCII or UTF-8 text files
*** one for create ASCII or UTF-8 text files from BASIC AMSDOS files
*** (this can already be done with manageDSK for files inside a DSK, maybe extract the code from there)
** data manipulation tools :
*** ability to arrange data files for example modify bytes order in a picture file by using Gray code capabilities for changing line with modifying 1 bit

== Windows ==

=== Cross Assemblers ===

*[[Tasm|tasm]]
*[[Pasmo|Pasmo]]
*[[ZMac|ZMac]]
*[http://little-bat.de/prog/ zasm]
*[[WinApe|WinApe]]'s built in assembler
* [[naken_asm]] [https://www.mikekohn.net/micro/naken_asm.php]

=== Cross compilers (C) ===

For tutorial, see http://www.cpcmania.com/Docs/Programming/Programming.htm by Mochilote

* [[Z88DK]]
* [[SDCC]], notably [[SDCC and CPC]] had hints and practical examples about the principles of writing in C for CPC.
* [[PhrozenC]]

=== Cross compilers (Java) ===

WIP

* [[JavaGrinder]]

=== Graphics ===

*[[AMSprite|AMSprite]] - Sprite/Loading Screen Editor and graphics conversion tools

=== Sound ===

*[[WYZTracker|WYZTracker]] - Music tracker / Sound effects editor
*[[Vortex Tracker]]

== Testing on a real CPC ==

=== For cassette ===

* 2CDT to add the files to a Cassette Image File (CDT)
* Tape2WAV to convert the Cassette Image file (CDT) into a WAV file.
* Then you can run the program on the emulator the same way as you would run it on a real CPC, or
* Connect your CPC (CPC664 and CPC6128 have a cassette input) to the Line-Out output of your PC soundcard
* On the CPC type:

|TAPE:RUN"

* Start your WAV player
* Set the volume to maximum
* play the WAV file
* Wait for the program to load...

=== For disc ===

* Use CPCFS or CPCXFS to put the binary files into a Disk Image file (DSK)
* Then you can run the program on the emulator the same way as you would run it on a real CPC

If your CPC has a 3.5" disc drive then the easiest method is to transfer the DSK to a 3.5" disc using the PC.

- Then use CPCDiskXP to write the DSK to a 3.5" disc drive - Put the disc into your CPC's 3.5" disc drive and type - |B: RUN "<gamename>

== Snapshots ==

The fastest way of testing your code on an emulator is by creating a snapshot. Use [[CPCSnapshot]] to insert your assembled code into a snapshot file. Then just load the snapshot file into the emulator. Windows users may also try WinAPE's integrated assembler which assembles the code directly into the emulated CPC's memory.

== Web links ==

* [http://ramlaid.free.fr/Amstrad/English/crossDev.htm CPC Cross Development tools by Ramlaid] (Link broken as 2012-01-08. If you can help, please update.)

[[Category:Programming]] [[Category:CrossDev]]