Amiga Docs

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Setting up a basic C/C++ development environment =====

TODO: Pro's and cons of the various alternatives (vbcc, gcc, others?)

===== Preconfigured environments ====

=== AmiDevCpp ====

As an alternative to developing on the Amiga itself, you can cross compile. AmiDevCpp provides a Windows based IDE and compilers.

=== MorphOS ====

Download [[http://www.morphos-team.net/downloads.html | MorphOS Software Development Kit]] and follow instructions. The development kit includes Scribble development environment, GCC, make and other tools.

===== Setting up vbcc =====

  * [[http://sun.hasenbraten.de/vbcc/|Vbcc]] is an optimizing C compiler that can run on and generate code for a variety of platforms, including all Amiga-like platforms except AROS. It can also run on (but not generate binaries for) Linux on x86. As a result it is well suited for cross compilation of apps that should run on the various Amiga platforms. To cover AROS as well, you will need a separate compiler (gcc port, see below).

===== Setting up gcc =====

=== MorphOS ====

Download [[http://www.morphos-team.net/downloads.html | MorphOS Software Development Kit]] and follow instructions.

=== Other ===
FIXME

===== Shared tools =====

 * [[http://aminet.net/package/dev/misc/AutoRev|Autorev]] is a tool to auto-update header contents with versioning/date information

==== Make ====

  * [[http://aminet.net/package/dev/gg/make-bin|Port of make]]

==== Fd2pragma ====

AmigaOS uses "fd" files to describe the API to libraries. Fd2pragma is a tool that generates various types of header files and link libraries to handle interfacing to the libraries. For most system libraries the appropriate files should be includes in the NDK, but for third party libraries you may need to generate the header files yourself using this tool.

FIXME
Amiga Docs

User Tools

Site Tools

Page Tools
