Code64 logo
 

Cross Development

Use that PC for something good!

Setting up a cross development environment

Debugging

Graphics conversion

Assemblers and Cross-dev systems

Have a look at the Source code conversion page if you want to know how to convert your sources from turbo assembler (petscii) to ascii, and how to (re)indent code that is messy. Also note that there is a list of commonly used assemblers on the Most used tools page.

ACME

  • ACME win32 binary and ACME source includes some tweaks I made from the base ACME 0.93 tree to add some development helpers when using the Microsoft Visual Studio IDE:
    • Compiler fixes for Microsoft Visual Studio 6.0
    • Added –msvc to output warnings/erros in the MS IDE format. Pressing F4 in the IDE will jump to the next warning/error.
    • Added –vicelabeldump and the PO !svl to save referenced global labels in VICE monitor format. When loaded in the monitor these labels are displayed in the disassembly.
    • Added the PO !sal to cause !sl and !svl to save all referenced labels including local labels. This is useful if separate zones have labels you want to know while debugging.

PDS (Programmers Development System)

  • PDS - Info and resources related to PDS

Coding tips

The tips to be posted here should be related either to issues specific to cross assembly, or even to the usage of specific cross assemblers.

ca65

Kick Assembler

Syntax Highlighting

Ways to transfer your code to C64

  • Final replay and Codenet - by Graham/Oxyron. Requires a cartridge with RR-net.
  • RR.exe - by Groepaz/Hitmen. Requires a Retro Replay cartdrige with SilverSurfer.
 
base/crossdev.txt · Last modified: 2010/09/01 14:24 by ftc
 
Code64 logo
Recent changes RSS feed Creative Commons License Driven by DokuWiki