summaryrefslogtreecommitdiffstats
path: root/doc/started/buildrt.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-04-10 16:03:26 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-04-10 16:03:26 +0000
commitbdec27096aeae0838d6ccb62344387c76b2a1086 (patch)
tree206859bf693c89ac7feae70159cf8b92e0be6b8d /doc/started/buildrt.t
parent9c2b0879e21293480486c105a2631d0590220e02 (diff)
downloadrtems-bdec27096aeae0838d6ccb62344387c76b2a1086.tar.bz2
In texinfo nicely with all version dependent information
now in variables and some updates already in place.
Diffstat (limited to 'doc/started/buildrt.t')
-rw-r--r--doc/started/buildrt.t40
1 files changed, 22 insertions, 18 deletions
diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t
index ea3069236d..daaf72f88b 100644
--- a/doc/started/buildrt.t
+++ b/doc/started/buildrt.t
@@ -16,49 +16,53 @@ tools directory:
@example
cd tools
-tar xzf ../arc/rtems-980219.tgz
+tar xzf ../arc/@value{RTEMS-TAR}
@end example
@section Add the bin directory under the install point to the default PATH
-Use the following command to append the <INSTALL_POINT>/bin directory to
-the PATH variable:
+In order to compile RTEMS, you must have the cross compilation toolset
+in your search patch. The following command appends the directory
+where the tools were installed in the previous chapter:
@example
-PATH=$PATH:<INSTALL_POINT>/bin
+export PATH=$PATH:<INSTALL_POINT>/bin
@end example
+NOTE: The above command is in Bourne shell (@code{sh}) syntax and should work with
+the Korn (@code{ksh}) and GNU Bourne Again Shell (@code{bash}). It will not
+work with the C Shell (@code{csh})or derivatives of the C Shell.
+
@section Generate RTEMS for a specific target and board support package
Make a build directory under tools and build the RTEMS product in this
-directory. The ../rtems-980219/configure command has numerous command line
+directory. The ../@value{RTEMS-UNTAR}/configure
+command has numerous command line
arguments. These arguments are discussed in detail in documentation that
comes with the RTEMS distribution. In the installation described in the
section "Unpack the RTEMS source", these configuration options can be found
-in file:
+in file tools/@value{RTEMS-UNTAR}/README.configure.
-@example
-tools/rtems-980219/README.configure
-@end example
-
-A simple example of the configuration appears below:
+The following shows the command sequence required to configure,
+compile, and install RTEMS with the POSIX API, KA9Q TCP/IP,
+and C++ support disabled. RTEMS will be built to target
+the @code{BOARD_SUPPORT_PACKAGE} board.
@example
mkdir build-rtems
cd build-rtems
-../rtems-980219/configure --target=<TARGET_CONFIGURATION> \
---disable-posix --disable-ka9q --disable-cpp \
---enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\
---prefix=< INSTALL_POINT>
+../@value{RTEMS-UNTAR}/configure --target=<TARGET_CONFIGURATION> \
+ --disable-posix --disable-ka9q --disable-cxx \
+ --enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\
+ --prefix=<INSTALL_POINT>
gmake all install
@end example
Where:
-The current summary of <TARGET_CONFIGURATION>'s and
+The list of currently supported of <TARGET_CONFIGURATION>'s and
<BOARD_SUPPORT_PACKAGE>'s can be found in
-tools/rtems-980219/README.configure
-
+tools/@value{RTEMS-UNTAR}/README.configure.
<INSTALL_POINT> is the installation point from the previous step
"Modify the bit script" in the build of the tools.