source: rtems-docs/user/installation/releases.rst

Last change on this file was d5b631f, checked in by Chris Johns <chrisj@…>, on Feb 27, 2019 at 9:36:39 PM

User: Change output block to type none.

  • Property mode set to 100644
File size: 19.4 KB

Releases

?
.. index:: tarball
?
.. index:: release

RTEMS releases provide a stable version of the kernel for the supported architectures. RTEMS maintaines the current and previous releases. Support for older releases is provided using the RTEMS support channels.

Please read :ref:`development-host` before continuing. The following procedure assumes you have installed and configured your host operating. It also assumes you have installed any dependent packages needed when building the tools and the kernel.

?

You need to select a location to build and install the RTEMS Tool chain and RTEMS. Make sure there is plenty of disk space and a fast disk is recommended. Our procedure will document building and installing the tools in a base directory called :file:`/opt/rtems`. This path will require root access. If you are working on a machine you do not have root access to you can use a home directory, If building on Windows use :file:`/c/opt/rtems` to keep the top level paths as short as possible. :ref:`windows-path-length` provides more detail about path lengths on Windows.

???

The location used to install the tools and kernel is called the prefix. :ref:`QuickStartPrefixes` explains prefixes and how to use them. It is best to have a prefix for each different version of RTEMS you are using. If you are using RTEMS 4.11 in production it is not a good idea to install a development version of 5 over the top by using the same prefix as the 4.11 build. A separate prefix for each version avoids this.

?

Released versions of the RTEMS Source Builder (RSB) downloads all source code for all packages from the :r:url:`ftp` rather than from the package's home site. Hosting all the source on the :r:url:`ftp` ensures the source is present for the life of the release on the :r:url:`ftp`. If there is a problem accessing the RTEMS FTP the RSB will fall back to the packages home site.

???

The :r:url:`ftp` is hosted at the Oregon State University's The Open Source Lab (http://osuosl.org/). This is a nonprofit organization working for the advancement of open source technologies and RTEMS is very fortunate to be shosted here. It has excellent internet access and performance.

?

Note

Controlling the RTEMS Kernel Build

Building releases by default does not build the RTEMS kernel. To build the RTEMS kernel add the --with-rtems option to the RSB command line.

By default all the BSPs for an architecture are built. If you only wish to have a specific BSP built you can specify the BSP list by providing to the RSB the option --with-rtemsbsp. For example to build two BSPs for the SPARC architecture you can supply --with-rtemsbsp="erc32 leon3". This can speed the build time up for some architectures that have a lot of BSPs.

Once you have built the tools and kernel you can move to the Packages section of the manual.

RTEMS Tools and Kernel

This procedure will build a SPARC tool chain. Set up a suitable workspace to build the release in. On Unix:

Error: Failed to load processor none
No macro or processor named 'none' found

If building on Windows:

Error: Failed to load processor none
No macro or processor named 'none' found

Note the paths on Windows will be different to those shown.

Download the RTEMS Source Builder (RSB) from the RTEMS FTP server:

Error: Failed to load processor none
No macro or processor named 'none' found

On Unix unpack the RSB release tar file using:

Error: Failed to load processor none
No macro or processor named 'none' found

On Windows you need to shorten the path (See :ref:`windows-path-length`) after you have unpacked the tar file:

?
Error: Failed to load processor none
No macro or processor named 'none' found

Build a tool chain for the SPARC architecure. We are using the SPARC architecture in our example because GDB has a good simulator that lets us run and test the samples RTEMS builds by default

If building on Windows add --jobs=none to avoid GNU make issues on Windows discussed in :ref:`msys2_parallel_builds`.

?
Error: Failed to load processor none
No macro or processor named 'none' found

You can now build a third-party library or an application as defaulted in TBD.

Note: See TracBrowser for help on using the repository browser.