GCCSDK: Difference between revisions
m (Remove "Upgrading from older releases", it's no longer applicable) |
m (Drop 'next release = shared libs' comment as it is outdated; Drop 'GCCSDK Source repository' (more appropriately mentioned in 'Using GCCSDK')) |
||
| Line 9: | Line 9: | ||
There also exist front ends for other languages, such as Fortran, Objective C, Ada 9X, Modula-3, Pascal, Cobol and Java, however these have not been ported to run on RISC OS at this time. Some of these are present, but unsupported, in older versions of RISC OS GCC. |
There also exist front ends for other languages, such as Fortran, Objective C, Ada 9X, Modula-3, Pascal, Cobol and Java, however these have not been ported to run on RISC OS at this time. Some of these are present, but unsupported, in older versions of RISC OS GCC. |
||
The current version of GCC for RISC OS is 4.1.1 which is based on [http://en.wikipedia.org/wiki/Executable_and_Linkable_Format ELF Object format] and binutils |
The current version of GCC for RISC OS is 4.1.1 which is based on [http://en.wikipedia.org/wiki/Executable_and_Linkable_Format ELF Object format] and binutils. Previous releases were based on GCC 3.4 and targets the traditional RISC OS AOF and AIF targets. |
||
* [[GCC for RISC OS]] |
* [[GCC for RISC OS]] |
||
| Line 20: | Line 20: | ||
GCCSDK can be used to compile and develop GCC and UnixLib itself, or as the basis for a cross-compiling system. It includes a number of "porting scripts" which automate the process of building and configuring new ports, which would otherwise be difficult and error prone, and not possible when done natively under RISC OS. |
GCCSDK can be used to compile and develop GCC and UnixLib itself, or as the basis for a cross-compiling system. It includes a number of "porting scripts" which automate the process of building and configuring new ports, which would otherwise be difficult and error prone, and not possible when done natively under RISC OS. |
||
* [[Using GCCSDK]] |
|||
=== GCCSDK Autobuilder === |
=== GCCSDK Autobuilder === |
||
| Line 45: | Line 47: | ||
See [[Bug Reporting]] on how to submit bug reports against GCCSDK. |
See [[Bug Reporting]] on how to submit bug reports against GCCSDK. |
||
= GCCSDK Source Repository = |
|||
See [[source repositories overview]] for how to access GCCSDK source. |
|||
{{GCC and GCCSDK pages}} |
{{GCC and GCCSDK pages}} |
||
Revision as of 15:01, 30 May 2010
Introduction
The riscos.info GCCSDK is really two closely related sub-projects - GCC for RISC OS, the RISC OS port of GCC, and GCC Software Development Kit, the environment for developing GCC and porting programs to RISC OS. The latter is actually used to create the former. The documentation is split accordingly.
GCC for RISC OS
GCC for RISC OS is a complete, free and fully-featured compiler solution for RISC OS based on the GNU Compiler Collection. It can compile C and C++ using modern standards and assemble ARM code. It also includes support for RISC OS modules, and usage of the native RISC OS Shared C Library, or the bundled Unix-compatibility library UnixLib as runtime library. It aims to be feature complete above and beyond the commercial Castle Technology Ltd's C/C++ compiler suite.
There also exist front ends for other languages, such as Fortran, Objective C, Ada 9X, Modula-3, Pascal, Cobol and Java, however these have not been ported to run on RISC OS at this time. Some of these are present, but unsupported, in older versions of RISC OS GCC.
The current version of GCC for RISC OS is 4.1.1 which is based on ELF Object format and binutils. Previous releases were based on GCC 3.4 and targets the traditional RISC OS AOF and AIF targets.
GCC Software Development Kit
GCCSDK
GCC Software Development Kit (GCCSDK) is a portable build environment for creating RISC OS executables to be run natively on RISC OS. The build environment is designed to be hosted on a Unix-like system, such as GNU/Linux, FreeBSD, Solaris, MacOS X or even Windows (under Cygwin). GCCSDK releases are tied-in with the corresponding GCC releases.
GCCSDK can be used to compile and develop GCC and UnixLib itself, or as the basis for a cross-compiling system. It includes a number of "porting scripts" which automate the process of building and configuring new ports, which would otherwise be difficult and error prone, and not possible when done natively under RISC OS.
GCCSDK Autobuilder
The autobuilder is a powerful system for automatically fetching, configuring and building of sources and dependencies for programs, making use of the porting scripts. Done manually, such a process would be tedious, time-consuming and error prone. Once a program is added to the autobuilder, other developers can easily reproduce the work, and concentrate on the important details.
The autobuilder presently includes instructions for building around 150 libraries and programs for RISC OS.
Development
The status of the current GCCSDK development can be found at GCCSDK Development.
GCCSDK GCC Releases
All recent GCCSDK GCC Releases can be found on the downloads page. Details on what is changed in each release can be found at GCCSDK Releases.
Mailing list
A mailing list exists for GCCSDK discussions.
Bug reporting
See Bug Reporting on how to submit bug reports against GCCSDK.
| GCC and GCCSDK pages |
| GCC under RISC OS GCC for RISC OS, GCC tutorial, GCC common switches, GCC for beginners, UnixLib, ELFLoader |
