From 0fcd2cecd36fbc8c04ab3378e0bfbf9ef3252951 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Mon, 8 May 2000 16:14:25 +0000 Subject: Now sharing the "buildrt.t" or Building RTEMS chapter with the C version of Getting Started. --- doc/started_ada/Makefile.am | 4 ++ doc/started_ada/buildrt.t | 142 -------------------------------------------- 2 files changed, 4 insertions(+), 142 deletions(-) delete mode 100644 doc/started_ada/buildrt.t (limited to 'doc/started_ada') diff --git a/doc/started_ada/Makefile.am b/doc/started_ada/Makefile.am index e1d7fc37e9..6aed6bdb55 100644 --- a/doc/started_ada/Makefile.am +++ b/doc/started_ada/Makefile.am @@ -22,6 +22,9 @@ FILES= tversions.texi info_TEXINFOS = started_ada.texi started_ada_TEXINFOS = $(FILES) $(COMMON_FILES) $(GENERATED_FILES) +buildrt.t: $(top_srcdir)/started/buildrt.t + $(LN_S) $< + intro.texi: intro.t tversions.texi $(BMENU) -c -p "Top" \ -u "Top" \ @@ -53,3 +56,4 @@ gdb.texi: gdb.t tversions.texi -n "" $< EXTRA_DIST = *.t +CLEANFILES += buildrt.t diff --git a/doc/started_ada/buildrt.t b/doc/started_ada/buildrt.t deleted file mode 100644 index 9d5b95e150..0000000000 --- a/doc/started_ada/buildrt.t +++ /dev/null @@ -1,142 +0,0 @@ -@c -@c -@c COPYRIGHT (c) 1988-1999. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Building RTEMS - -@section Unpack the RTEMS Source - -Use the following command sequence to unpack the RTEMS source into the -tools directory: - -@example -cd tools -tar xzf ../archive/@value{RTEMS-TAR} -@end example - -@section Add /bin to Executable PATH - -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 -export PATH=$PATH:/bin -@end example - -@b{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 Verifying the Operation of the Cross Toolset - -In order to insure 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 more, @code{gcc} prints out information -showing where it found the subprograms it invokes. Place the following -function in a file named @code{f.c}: - -@example -int f( int x ) -@{ - return x + 1; -@} -@end example - -Then assemble the file using a command similar to the following: - -@example -m68k-rtems-gcc -v -S f.c -@end example - -Where @code{m68k-rtems-gcc} should be changed to match the installed -name of your cross compiler. The result of this command will be -a sequence of output showing where the cross-compiler searched for -and found its subcomponents. Verify that these paths correspond -to your . - -@b{NOTE:} 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}. This can result in very confusing -error messages. - -@section Generate RTEMS for a Specific Target and BSP - -@subsection Using the bit_rtems script - -The simplest way to build RTEMS is to use the @code{bit_rtems} script. -This script interprets the settings in the @code{user.cfg} file to -enable or disable the various RTEMS options. - -This script is invoked as follows: - -@example -./bit_rtems CPU [BSP] -@end example - -Where CPU is one of the RTEMS supported CPU families from the following -list: - -@itemize @bullet -@item hppa1.1 -@item i386 -@item i386-elf -@item i386-go32 -@item i960 -@item m68k -@item mips64orion -@item powerpc -@item sh -@item sparc -@end itemize - -BSP is a supported BSP for the selected CPU family. The list of -supported BSPs may be found in the file -tools/@value{RTEMS-UNTAR}/README.configure -in the RTEMS source tree. If the BSP parameter is not specified, -then all supported BSPs for the selected CPU family will be built. - -@b{NOTE:} The POSIX API must be enabled to use GNAT/RTEMS. - -@subsection Using the RTEMS configure Script Directly - -Make a build directory under tools and build the RTEMS product in this -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 the file tools/@value{RTEMS-UNTAR}/README.configure. - -The GNAT/RTEMS run-time implementation is based on the POSIX API. Thus -the RTEMS configuration for a GNAT/RTEMS environment MUST include the -@code{--enable-posix} flag. - -The following shows the command sequence required to configure, -compile, and install RTEMS with the POSIX API enabled. -RTEMS will be built to target the @code{BOARD_SUPPORT_PACKAGE} board. - -@example -mkdir build-rtems -cd build-rtems -../@value{RTEMS-UNTAR}/configure --target= \ - --enable-posix \ - --enable-rtemsbsp=\ - --prefix= -make all install -@end example - -Where the list of currently supported of 's and -'s can be found in -tools/@value{RTEMS-UNTAR}/README.configure. - - is the installation point from the previous step -"Modify the bit_ada Script" in the build of the tools. - -NOTE: The @code{make} utility used should be GNU make. - -- cgit v1.2.3