path: root/doc/started/buildrt.t
diff options
authorGedare Bloom <>2015-03-11 10:29:13 -0400
committerGedare Bloom <>2015-03-11 13:39:29 -0400
commitd84995d28c141fd6eb0f04606ea35caa316b9eb7 (patch)
tree8457e82327fd512769d2140a6393ae42b2926795 /doc/started/buildrt.t
parentcf4045630e1dd59221c67005ca1652b4350ad8eb (diff)
doc/started: simplify and fix
* fix and remove some macros in * refer to devel mailing list. * remove reference to Debian packaging in requirements section. * remove section on prebuilt tools. * replace toolset build instructions with link to RSB docs. * Add a note in building RTEMS section about using RSB. * Fix URLs Closes #2291.
Diffstat (limited to 'doc/started/buildrt.t')
1 files changed, 16 insertions, 12 deletions
diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t
index 5adf5477ef..549e3094df 100644
--- a/doc/started/buildrt.t
+++ b/doc/started/buildrt.t
@@ -5,6 +5,11 @@
@chapter Building RTEMS
+@b{NOTE}: If you built your toolset with RSB, by default the RSB also
+builds RTEMS while building the compiler toolset. You may already have
+a built and installed RTEMS in this case, and if not you should check
+the RSB documentation at @uref{,}.
@section Obtain the RTEMS Source Code
This section provides pointers to the RTEMS source code and example
@@ -14,8 +19,8 @@ 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{,}
-@item @uref{,}
+@item @uref{,}
+@item @uref{,}
@end itemize
Associated with each RTEMS Release is a set of example programs.
@@ -47,7 +52,7 @@ Instead of downloading release tarballs you may choose to check out the current
RTEMS source from the project's source code repository. For details on
accessing the RTEMS source repository consult:
@section Add <INSTALL_POINT>/bin to Executable PATH
@@ -56,8 +61,8 @@ in your search path. It is important to have the RTEMS toolset first
in your path to ensure that you are using the intended version of all
tools. The following command prepends the directory where
the tools were installed in a previous step. If you are using
-binaries provided by the RTEMS Project, the <INSTALL_POINT> will be
+binaries installed to @code{/opt/rtems-@value{RTEMSAPI}}, then the
+<INSTALL_POINT> will be @code{/opt/rtems-@value{RTEMSAPI}}
export PATH=<INSTALL_POINT>/bin:$@{PATH@}
@@ -106,11 +111,9 @@ m68k-rtems@code{RTEMSAPI}-gcc -v -c f.c
@end example
If this produces messages that indicate the assembly code is not valid,
-then it is likely that you have fallen victim to one of the problems
-described in @ref{Error Message Indicates Invalid Option to Assembler}
-Please do not feel bad about this and do not give up, one of the most
-common installation errors is for the cross-compiler not to be able
-to find the cross assembler and default to using the native @code{as}.
+then it is likely that you have fallen victim to one of the most
+common installation errors and the cross-compiler is not able
+to find the cross assembler and defaults to using the native @code{as}.
This can result in very confusing error messages.
@section Building RTEMS for a Specific Target and BSP
@@ -162,8 +165,9 @@ the @code{BOARD_SUPPORT_PACKAGE} board.
mkdir build-rtems
cd build-rtems
-../rtems-@value{RTEMSAPI}.VERSION/configure --target=<TARGET_CONFIGURATION> \
- --disable-posix --disable-networking --disable-cxx \
+../rtems-@value{RTEMSAPI}.VERSION/configure \
+ --disable-networking \
make all