Getting Started with RTEMS
The tool versions and patch revisions change on a fairly frequent basis. In addition, these may vary based upon the target architecture. In some cases, the RTEMS Project may have to stick with a particular version of a tool to provide a working version for a specific architecture. Because of this, it is impossible to provide this information in a complete and accurate manner in this manual. You will need to refer to the configuration files used by the RTEMS RPM specification files to determine the current versions and, if a patch is required, what version. This section describes how to locate the appropriate tool versions and patches for a particular target architecture.
All patches and RPM specification files are kept in CVS. They are not included in release tarballs. You will have to access the CVS branch for RTEMS 4.9. For details on this, visit http://www.rtems.org and look for instructions on accessing the RTEMS Source Code Repository in read-only mode.
In the checked out source code, you will need to look in the subdirectory
contrib/crossrpms/autotools to determine the versions of AUTOCONF
and AUTOMAKE as well as any patches required. In this directory are
a few files you will need to look at. The first is Makefile.am
which defines the versions of AUTOCONF and AUTOMAKE required for this
RTEMS Release Series. Make a note of the version numbers required for
AUTOCONF and AUTOMAKE. Then examine the following files to determine
the master location for the source tarballs and to determine if a patch
is required for each tool version cited in the Makefile.am.
autoconf-sources.add automake-sources.add
If any patches are required, they will be in the
contrib/crossrpms/patches subdirectory of your checked out RTEMS
source tree.
In the checked out source code, you will need to look in the subdirectory
contrib/crossrpms/rtems4.9 to determine the target
specific tool versions and patches required. In this directory, you
will find a number of subdirectories with many named after target
architectures supported by RTEMS. Descend into the directory for the
architecture you plan to build tools for. Again, the Makefile.am
defines the tool versions for this architecture and RTEMS Release Series.
Make a note of the version numbers required for BINUTILS, GCC, NEWLIB,
and GDB. Then examine the following files to determine the master
location for the source tarballs and to determine if a patch is required
for each tool version cited in the Makefile.am.
binutils-sources.add gcc-sources.add gdb-sources.add
If any patches are required, they will be in the
contrib/crossrpms/patches subdirectory of your checked out RTEMS
source tree.
This is the entire set of source tarballs and patches required for a toolset targeting the selected architecture. In many cases, this will be the same versions required by other targets on this RTEMS Release Series.
Depending on the build method chosen, you may have to download source and patches or only patches. Also the destination directory for the downloaded source is dependent on the build method followed. But the versions required are the same. Specific information on what to download and where to place it is in subsequent sections.
Getting Started with RTEMS
Copyright © 1988-2008 OAR Corporation