GCC for RISC OS

From RISC OS

(Difference between revisions)
Jump to: navigation, search
(Added references to ProfileMod and dmalloc port)
Line 49: Line 49:
* [http://www.reallysmall.co.uk/Pages/normal/software/development/sourcery/sourcery.html Sourcery] : Sourcery will manage the source code that makes up a project but it will also manage the various resources files that are required to produce a RISC OS application. These include Sprite, Message and Template files.
* [http://www.reallysmall.co.uk/Pages/normal/software/development/sourcery/sourcery.html Sourcery] : Sourcery will manage the source code that makes up a project but it will also manage the various resources files that are required to produce a RISC OS application. These include Sprite, Message and Template files.
 +
* [http://adrian.aemulor.com/udp.html ProfileMod] : ProfileMod can be used to profile your code at expense of having to recompile it with the GCC option -finstrument-functions.
 +
* [http://www.riscos.info/websvn/listing.php?repname=gccsdk&path=%2Ftrunk%2Fautobuilder%2Fdevelop%2Fdmalloc%2F&rev=0&sc=0 dmalloc port] : [http://dmalloc.com/ dmalloc] can be used to find memory leaks or memory corruptions due to wrong malloc()/free()/etc. use.  It has been ported to RISC OS and is currently located in [[Using_GCCSDK#GCCSDK_Autobuilder_Usage|GCCSDK Autobuilder]] in the develop/dmalloc subdirectory.
== Links ==
== Links ==
* [[GCCSDK|GCC/GCCSDK home]]
* [[GCCSDK|GCC/GCCSDK home]]

Revision as of 21:34, 12 November 2006

Contents

Using GCC under RISC OS

Setup

GCC is very easy to setup on RISC OS. The following is what you need to get started with a fully working C compiler.

Additional languages and tools

You may also wish to install one or more of the following components as well :

RISC OS GCC Tutorials and information

In addition, the !gcc application itself contains a number of examples (inside !gcc.examples).

Distributing GCC compiled programs

When you distribute a GCC compiled program and are using the SharedCLibrary as runtime library (i.e. using option -mlibscl), then no additional support files need to be made available with your program.

On the other hand when you are using UnixLib as runtime library (and that's the default runtime library), then an up-to-date version of some UnixLib support modules need to be used together with your program. The following is an overview of these support modules :

The modules SharedUnixLibrary, Digital Renderer, Iconv and CryptRandom will be RMEnsure'd with their minimal needed version number by the UnixLib code at the moment their functionality is needed. Appropriate error message will be returned when these modules are not available or when they do not have a sufficent high enough version number.

When you distribute a copy of these UnixLib support modules with your program, please also mention the URLs in documentation and/or installation notes or program where up-to-date versions can be found.

Useful programs

The following list contains useful programs helping you to develop with GCC on RISC OS :

  • Sourcery : Sourcery will manage the source code that makes up a project but it will also manage the various resources files that are required to produce a RISC OS application. These include Sprite, Message and Template files.
  • ProfileMod : ProfileMod can be used to profile your code at expense of having to recompile it with the GCC option -finstrument-functions.
  • dmalloc port : dmalloc can be used to find memory leaks or memory corruptions due to wrong malloc()/free()/etc. use. It has been ported to RISC OS and is currently located in GCCSDK Autobuilder in the develop/dmalloc subdirectory.

Links

Personal tools