OAR

RTEMS 4.5.1-pre3 On-Line Library


Localizing the Configuration

PREV UP NEXT Bookshelf Getting Started with GNAT/RTEMS

3.11: Localizing the Configuration

Edit the user.cfg file to alter the settings of various variables which are used to tailor the build process. Each of the variables set in user.cfg may be modified as described below:

INSTALL_POINT
is the location where you wish the GNU C/C++ cross compilation tools for RTEMS to be built. It is recommended that the directory chosen to receive these tools be named so that it is clear from which gcc distribution it was generated and for which target system the tools are to produce code for.

WARNING: The INSTALL_POINT should not be a subdirectory under the build directory. The build directory will be removed automatically upon successful completion of the build procedure.

BINUTILS
is the directory under tools that contains binutils-2.10. For example:
BINUTILS=binutils-2.10
GCC
is the directory under tools that contains gcc-2.8.1. For example,
GCC=gcc-2.8.1

Note that the gnat version is not needed because the gnat source is built as part of building gcc.

NEWLIB
is the directory under tools that contains newlib-1.8.2. For example:
NEWLIB=newlib-1.8.2
BUILD_DOCS
is set to "yes" if you want to install documentation. This requires that tools supporting documentation production be installed. This currently is limited to the GNU texinfo package. For example:
BUILD_DOCS=yes
BUILD_OTHER_LANGUAGES
is set to "yes" if you want to build languages other than C and C++. At the current time, the set of alternative languages includes Java, Fortran, and Objective-C. These alternative languages do not always build cross. Hence this option defaults to "no".

For example:

BUILD_OTHER_LANGUAGES=yes

NOTE: Based upon the version of the compiler being used, it may not be possible to build languages other than C and C++ cross. In many cases, the language run-time support libraries are not "multilib'ed". Thus the executable code in these libraries will be for the default compiler settings and not necessarily be correct for your CPU model.

RTEMS
is the directory under tools that contails rtems-4.5.1.
ENABLE_RTEMS_POSIX
is set to "yes" if you want to enable the RTEMS POSIX API support. At this time, this feature is not supported by the UNIX ports of RTEMS and is forced to "no" for those targets. This corresponds to the configure option --enable-posix.

This must be enabled to support the GNAT/RTEMS run-time.

ENABLE_RTEMS_ITRON
is set to "yes" if you want to enable the RTEMS ITRON API support. At this time, this feature is not supported by the UNIX ports of RTEMS and is forced to "no" for those targets. This corresponds to the configure option --enable-itron.
ENABLE_RTEMS_MP
is set to "yes" if you want to enable the RTEMS multiprocessing support. This feature is not supported by all RTEMS BSPs and is automatically forced to "no" for those BSPs. This corresponds to the configure option --enable-multiprocessing.
ENABLE_RTEMS_CXX
is set to "yes" if you want to build the RTEMS C++ support including the C++ Wrapper for the Classic API. This corresponds to the configure option --enable-cxx.
ENABLE_RTEMS_TESTS
is set to "yes" if you want to build the RTEMS Test Suite. If this is set to "no", then only the Sample Tests will be built. Setting this option to "yes" significantly increases the amount of disk space required to build RTEMS. This corresponds to the configure option --enable-tests.
ENABLE_RTEMS_TCPIP
is set to "yes" if you want to build the RTEMS TCP/IP Stack. If a particular BSP does not support TCP/IP, then this feature is automatically disabled. This corresponds to the configure option --enable-tcpip.
ENABLE_RTEMS_NONDEBUG
is set to "yes" if you want to build RTEMS in a fully optimized state. This corresponds to executing make after configuring the source tree.
ENABLE_RTEMS_DEBUG
is set to "yes" if you want to build RTEMS in a debug version. When built for debug, RTEMS will include run-time code to perform consistency checks such as heap consistency checks. Although the precise compilation arguments are BSP dependent, the debug version of RTEMS is usually built at a lower optimization level. This is usually done to reduce inlining which can make tracing code execution difficult. This corresponds to executing make VARIANT=debug after configuring the source tree.
INSTALL_RTEMS
is set to "yes" if you want to install RTEMS after building it. This corresponds to executing make install after configuring and building the source tree.
ENABLE_RTEMS_MAINTAINER_MODE
is set to "yes" if you want to enabled maintainer mode functionality in the RTEMS Makefile. This is disabled by default and it is not expected that most users will want to enable this. When this option is enabled, the build process may attempt to regenerate files that require tools not required when this option is disabled. This corresponds to the configure option --enable-maintainer-mode.


PREV UP NEXT Bookshelf Getting Started with GNAT/RTEMS

Copyright © 1988-2000 OAR Corporation