diff options
Diffstat (limited to 'doc/started/buildrt.t')
| -rw-r--r-- | doc/started/buildrt.t | 41 |
1 files changed, 28 insertions, 13 deletions
diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t index 8c951b116f..a18f0d9847 100644 --- a/doc/started/buildrt.t +++ b/doc/started/buildrt.t @@ -13,9 +13,9 @@ This section provides pointers to the RTEMS source code and example programs. These files should be placed in your @code{archive} directory. The set of tarballs which comprise an RTEMS release is placed in a -directory whose name if the release on the ftp site. The RTEMS ftp site +directory whose name is the release on the ftp site. The RTEMS ftp site is accessible via both the ftp and http protocols at the following URLs: - + @itemize @bullet @item @uref{http://www.rtems.org/ftp/pub/rtems,http://www.rtems.org/ftp/pub/rtems} @item @uref{ftp://www.rtems.org/pub/rtems,ftp://www.rtems.org/pub/rtems} @@ -35,7 +35,7 @@ This new collection is called "Examples V2". It is contained in the file @section Unarchive the RTEMS Source Use the following command sequence to unpack the RTEMS source into the -tools directory: +tools directory: @example cd tools @@ -44,6 +44,20 @@ tar xjf ../archive/rtems-@value{RTEMSAPI}.<VERSION>.tar.bz2 This creates the directory rtems-@value{RTEMSAPI}.<VERSION> +@section Obtaining the RTEMS Source from CVS + +Instead of downloading release tarballs you may choose to check out the current +RTEMS source from CVS. For details on accessing RTEMS CVS repository consult +@uref{http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository, http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository}. The steps required +to obtain the source code from CVS are usually like the following: +@example +$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS login +Logging in to :pserver:anoncvs@@www.rtems.com:2401/usr1/CVS +CVS password: +$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P rtems # for the main RTEMS source +$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P examples-v2 # for examples +@end example + @section Add <INSTALL_POINT>/bin to Executable PATH In order to compile RTEMS, you must have the cross compilation toolset @@ -65,9 +79,9 @@ C Shell. @section Verifying the Operation of the Cross Toolset -In order to insure that the cross-compiler is invoking the correct +In order to ensure that the cross-compiler is invoking the correct subprograms (like @code{as} and @code{ld}), one can test assemble -a small program. When in verbose mode, @code{gcc} prints out information +a small program. When in verbose mode, @code{gcc} prints out information showing where it found the subprograms it invokes. In a temporary working directory, place the following function in a file named @code{f.c}: @@ -110,9 +124,9 @@ This can result in very confusing error messages. @section Building RTEMS for a Specific Target and BSP -This section describes how to configure and build RTEMS -so that it is specifically tailored for your BSP and the -CPU model it uses. There is currently only one supported +This section describes how to configure and build RTEMS +so that it is specifically tailored for your BSP (Board Support Package) +and the CPU model it uses. There is currently only one supported method to compile and install RTEMS: @itemize @bullet @@ -120,7 +134,7 @@ method to compile and install RTEMS: @end itemize Direct invocation of @code{configure} and @code{make} provides more control -and easier recovery from problems when building. +and easier recovery from problems when building. This section describes how to build RTEMS. @@ -133,8 +147,8 @@ discussed in detail in documentation that comes with the RTEMS distribution. A full list of these arguments can be obtained by running @code{../rtems-@value{RTEMSAPI}.<VERSION>/configure --help} If you followed the procedure described in the section @ref{Unarchive the -RTEMS Source}, these configuration options can be found in the file -tools/rtems-@value{RTEMSAPI}.<VERSION>/README.configure. +RTEMS Source} or @ref{Obtaining the RTEMS Source from CVS}, these configuration options can be found in the file +rtems-@value{RTEMSAPI}.<VERSION>/README.configure. @b{NOTE}: The GNAT/RTEMS run-time implementation is based on the POSIX API and the GNAT/RTEMS run-time cannot be compiled with networking @@ -144,7 +158,7 @@ MUST include the @code{--enable-posix --enable-networking} flag. The following shows the command sequence required to configure, compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP, -and C++ support disabled. RTEMS will be built to target +and C++ support disabled. RTEMS will be built to target the @code{BOARD_SUPPORT_PACKAGE} board. @example @@ -154,7 +168,8 @@ cd build-rtems --disable-posix --disable-networking --disable-cxx \ --enable-rtemsbsp=<BSP>\ --prefix=<INSTALL_POINT> -make all install +make all +make install @end example <TARGET> is of the form <CPU>-rtems@value{RTEMSAPI} and the list of |