2003-10-02 Joel Sherrill <joel@OARcorp.com>

* Makefile.am, binaries.t, buildc.t, intro.t, nextstep.t, require.t,
	sample.t, started.texi: General improvements and merge enough Ada
	information to justify dropping the Ada specific manual. There is
	likely still Ada specific information to merge though.
This commit is contained in:
Joel Sherrill committed 2003-10-02 18:01:48 +00:00
1 parent e931dbbeba
commit 48cd0b8e25
9 files changed
+249 -53

No files matched your search

+7
View File
@@ -1,3 +1,10 @@
2003-10-02 Joel Sherrill <joel@OARcorp.com>
* Makefile.am, binaries.t, buildc.t, intro.t, nextstep.t, require.t,
sample.t, started.texi: General improvements and merge enough Ada
information to justify dropping the Ada specific manual. There is
likely still Ada specific information to merge though.
2003-10-02 Chris Caudle <chris@chriscaudle.org>
* nextstep.t: RTEMS applications can now use main() so correct the
+2 -2
View File
@@ -36,7 +36,7 @@ require.texi: require.t tversions.texi
binaries.texi: binaries.t tversions.texi
$(BMENU2) -c -p "Archive and Build Directory Format" \
-u "Top" \
-n "Building the GNU C/C++ Cross Compiler Toolset" < $< > $@
-n "Building the GNU Cross Compiler Toolset" < $< > $@
buildc.texi: buildc.t tversions.texi
$(BMENU2) -c -p "Removing Zipped Tar Files" \
@@ -46,7 +46,7 @@ buildc.texi: buildc.t tversions.texi
buildrt.texi: buildrt.t tversions.texi
$(BMENU2) -c -p "Error Messages Indicating Configuration Problems" \
-u "Top" \
-n "Building the Sample Application" < $< > $@
-n "Building the Sample Applications" < $< > $@
sample.texi: sample.t tversions.texi
$(BMENU2) -c -p "Using the RTEMS configure Script Directly" \
+4 -2
View File
@@ -44,8 +44,8 @@ These binaries are strictly optional.
@end enumerate
NOTE: Installing toolset binaries does not install RTEMS itself, only the tools
required to build RTEMS. See @ref{Building RTEMS} for the next
NOTE: Installing toolset binaries does not install RTEMS itself, only
the tools required to build RTEMS. See @ref{Building RTEMS} for the next
step in the process.
@section RPMs
@@ -61,6 +61,7 @@ of a C/C++ toolset targeting the SPARC architecture.
rpm -i rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -i rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-c++-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -i rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
@@ -93,6 +94,7 @@ of a C/C++ toolset targeting the SPARC architecture.
rpm -e sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
rpm -e rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
rpm -e sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -e sparc-rtems-c++-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -e rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -e sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -e rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
+56 -9
View File
@@ -6,7 +6,7 @@
@c $Id$
@c
@chapter Building the GNU C/C++ Cross Compiler Toolset
@chapter Building the GNU Cross Compiler Toolset
NOTE: This chapter does @b{NOT} apply if you installed
prebuilt toolset executables for BINUTILS, GCC, NEWLIB,
@@ -537,15 +537,16 @@ ln -s ../@value{NEWLIBUNTAR}/newlib .
The following example illustrates the invocation of
@code{configure} and @code{make}
to build and install @value{BINUTILSUNTAR} for the
sparc-rtems target:
to build and install @value{GCCUNTAR} with only
C and C++ support for the sparc-rtems target:
@example
mkdir b-gcc
cd b-gcc
../@value{GCCUNTAR}/configure --target=sparc-rtems \
--with-gnu-as --with-gnu-ld --with-newlib --verbose \
--enable-threads --prefix=@value{RTEMSPREFIX}
--enable-threads --enable-languages="c,c++" \
--prefix=@value{RTEMSPREFIX}
make all
make info
make install
@@ -559,6 +560,47 @@ refer to the documentation for @value{GCCUNTAR} or
invoke the @value{GCCUNTAR} @code{configure} command with the
@code{--help} option.
@c
@c Building GCC with Ada Support
@c
@subheading Building GCC with Ada Support
If you want a GCC toolset that includes support for Ada
(e.g. GNAT), there are some additional requirements on
the host environment and additional build steps to perform.
It is critical that you use the same version of GCC/GNAT as
the native compiler. GNAT must be compiled with an Ada compiler
and when building a GNAT cross-compiler, it should be
the same version of GNAT itself.
The build procedure is the same until the configure step.
A GCC toolset with GNAT enabled requires that @code{ada}
be included in the set of enabled languages.
The following example illustrates the invocation of
@code{configure} and @code{make}
to build and install @value{GCCUNTAR} with only
C, C++, and Ada support for the sparc-rtems target:
@example
mkdir b-gcc
cd @value{GCCUNTAR}/gcc/ada
touch treeprs.ads [es]info.h nmake.ad[bs]
cd ../../../b-gcc
../@value{GCCUNTAR}/configure --target=sparc-rtems \
--with-gnu-as --with-gnu-ld --with-newlib --verbose \
--enable-threads --enable-languages="c,c++,ada" \
--prefix=@value{RTEMSPREFIX}
make all
make info
make -C gcc cross-gnattools
make -C gcc ada.all.cross
make -C gcc GNATLIBCFLAGS="USER_SELECTED_CPU_CFLAGS" gnatlib
make install
@end example
After @value{GCCUNTAR} is built and installed the
build directory @code{b-gcc} may be removed.
@c
@c Building the GNU Debugger GDB
@c
@@ -577,12 +619,17 @@ specific. The following configurations have been
successfully used with RTEMS applications:
@itemize @bullet
@item Sparc Instruction Simulator (SIS)
@item PowerPC Instruction Simulator (PSIM)
@item DINK32
@item BDM with 68360 and MPC860 CPUs
@item BDM with ColdFire, 683xx, MPC860 CPUs
@item Motorola Mxxxbug found on M68xxx VME boards
@item Motorola PPCbug found on PowerPC VME and CompactPCI boards
@item Motorola PPCbug found on PowerPC VME, CompactPCI, and MTX boards
@item ARM based Cogent EDP7312
@item PC's using various Intel and AMD CPUs including i386,
i486, Pentium and above, and Athlon
@item PowerPC Instruction Simulator in GDB (PSIM)
@item MIPS Instruction Simulator in GDB (JMR3904)
@item Sparc Instruction Simulator in GDB (SIS)
@item Sparc Instruction Simulator (TSIM)
@item DINK32 on various PowerPC boards
@end itemize
GDB is currently RTEMS thread/task aware only if you are using the
+1 -1
View File
@@ -16,7 +16,7 @@ have a background in Unix, these instructions should provide the bare
essentials for performing a setup of the following items:
@itemize @bullet
@item GNU C/C++ Cross Compilation Tools for RTEMS on your build-host system
@item GNU Cross Compilation Tools for RTEMS on your build-host system
@item RTEMS OS for the target
@item GDB Debugger
@end itemize
+2 -2
View File
@@ -10,7 +10,7 @@
@chapter Where To Go From Here
At this point, you should have successfully installed a
GNU C/C++ Cross Compilation Tools for RTEMS on your host system
GNU Cross Compilation Tools for RTEMS on your host system
as well as the RTEMS OS for the target host. You should
have successfully linked the "hello world" program. You
may even have downloaded the executable to that target
@@ -52,7 +52,7 @@ on the network services provided by RTEMS.
@end itemize
In addition, the following manuals from the GNU C/C++ Cross
In addition, the following manuals from the GNU Cross
Compilation Toolset include information on run-time services
available.
+1 -1
View File
@@ -9,7 +9,7 @@
@chapter Requirements
This chapter describes the build-host system requirements and initial steps
in installing the GNU C/C++ Cross Compiler Tools and RTEMS on a build-host.
in installing the GNU Cross Compiler Tools and RTEMS on a build-host.
@section Disk Space
+174 -34
View File
File diff suppressed because it is too large. Load diff
+2 -2
View File
@@ -80,9 +80,9 @@ This is the online version of the Getting Started with RTEMS for C/C++ Users.
* Introduction::
* Requirements::
* Prebuilt Toolset Executables::
* Building the GNU C/C++ Cross Compiler Toolset::
* Building the GNU Cross Compiler Toolset::
* Building RTEMS::
* Building the Sample Application::
* Building the Sample Applications::
* Where To Go From Here::
* Using MS-Windows as a Development Host::
@end menu