RTEMS Development Hosts

{| border="0" cellpadding="5" cellspacing="0" align="right"

! style="background:#efefef;" | |}

Most RTEMS developers use the GNU Development Tools from the ​Free Software Foundation including ​GNU Compiler Collection (GCC), ​GNU Binary Utilities (binutils), ​GNU Debugger (gdb), ​Autoconf, and ​Automake. These tools support many operating systems and are used by the RTEMS Project in a cross development setup. The RTEMS project recommends and encourages Linux as a development platform for RTEMS.

The RTEMS Project provides prebuilt tools for a variety of operating systems. Please refer to the appropriate section below for information on your particular operating system.

If you are interested in seeing support for another operating system, please contact JoelSherrill.

GNU/Linux RPM Based Distributions

The RTEMS Project maintains an APT/Yum Repository which contains prebuilt RPMs for the entire RTEMS Development Environment. There is a separate repository for RTEMS Release Series from 4.6 on.

Visit GNU/Linux RPM APT/Yum Repository for more details.

GNU/Linux Debian Based Distributions

There was a GSoC 2008 project to provide Debian packaging. So packaging is available but the student duplicated large numbers of files which would be best generated from a template by a script. He is supposed to be addressing this deficiency and it is hoped that a Debian repository will be established at OAR after this is done.

If you are interested in this, please consider sponsoring an RTEMS developer to move it forward. This requires hands-on system administrator and build farm setup.

Windows

The RTEMS Project provides executable installers for Windows. Currently Windows Vista and 64 bit Windows servers have not been tested. You can find information about the installer on the Windows Installers page.

• Supports Windows 2000 and Windows XP with ​MinGW built tools. The tools are available as Windows Installers.

• MinGW:Grub2:VMWare Development Environment Setup shows how to boot with Grub2 and simulate with VMWare, and a further example of how to use such host environment to develop applications involving peripherals is detailed in Simulate Serial Communication Application. And information about how serial port is utilized for remote debugging can be found at RTEMS Eclipse Plug-in.

In the past, the RTEMS Project has provided binaries for ​Cygwin. There is nothing wrong with Cygwin, there are just so many hours in the day. If this interests you ​sponsor Cygwin support and/or volunteer to help.

The FreeBSD Operating System

NOTE: These do not appear to track the RTEMS Project updates very closely. And they do NOT follow RTEMS standard conventions on including a version number in the target name. You are very likely better off building from source. Caveat emptor!

FreeBSD's ports collection contains up-to-date version of gnu-tools, which is suitable for rtems development. There's even preconfigured ports/packages for the most popular architectures, namely:

• arm
• i386
• m68k
• mips
• powerpc
• sh
• sparc.

They either can be installed as pre-build packages, if available for your platform, or build via ports, e.g.:

cd /usr/ports/devel/sparc-rtems-gcc && make install cd /usr/ports/devel/sparc-rtems-gdb && make install

You can also specify default cpu optimization and FPU type for gcc, e.g.:

cd /usr/ports/devel/powerpc-rtems-gcc && make WITH_CPU=860 WITH_FLOAT_TYPE=soft

If you want to build rtems toolchain for architecture not available as slave port, you can build it directly using cross-binutils/cross-gcc/cross-gcc ports. For example, to build gcc toolchain for the cris microprocessor, issue the following:

cd /usr/ports/devel/cross-gcc && make TGTARCH=cris TGTABI=rtems WITH_RTEMS_PATCHES=yes

MacOS X

A number of users report success building their own local RTEMS tools from source.

NetBSD/OpenBSD

Building the tools from source is the best option currently.

=Other Environments=

It is recommended that you build from source.