Changeset bdec2709 in rtems


Ignore:
Timestamp:
Apr 10, 1998, 4:03:26 PM (24 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
8a3fd66
Parents:
9c2b087
Message:

In texinfo nicely with all version dependent information
now in variables and some updates already in place.

Location:
doc/started
Files:
8 edited

Legend:

Unmodified
Added
Removed
  • doc/started/Makefile

    r9c2b087 rbdec2709  
    2222    require.texi sample.texi
    2323
    24 FILES= $(PROJECT).texi $(GENERATED_FILES)
     24FILES= $(PROJECT).texi versions.texi $(GENERATED_FILES)
    2525
    2626INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*)
     
    4545        texi2dvi -v $(PROJECT).texi
    4646
    47 intro.texi: intro.t
     47intro.texi: intro.t versions.texi
    4848        $(BMENU) -c -p "Top" \
    4949            -u "Top" \
    5050            -n "Requirements" ${*}.t
    5151
    52 require.texi: require.t
     52require.texi: require.t versions.texi
    5353        $(BMENU) -c -p "Introduction" \
    5454            -u "Top" \
    5555            -n "Building the GNU C/C++ Cross Compiler Toolset" ${*}.t
    5656
    57 buildc.texi: buildc.t
     57buildc.texi: buildc.t versions.texi
    5858        $(BMENU) -c -p "Requirements" \
    5959            -u "Top" \
    6060            -n "Building RTEMS" ${*}.t
    6161
    62 buildrt.texi: buildrt.t
     62buildrt.texi: buildrt.t versions.texi
    6363        $(BMENU) -c -p "GNU C/C++ cross compiler toolset complete" \
    6464            -u "Top" \
    6565            -n "Building the Sample Application" ${*}.t
    6666
    67 sample.texi: sample.t
     67sample.texi: sample.t versions.texi
    6868        $(BMENU) -c -p "Generate RTEMS for a specific target and board support package" \
    6969            -u "Top" \
    7070            -n "Building the GNU Debugger" ${*}.t
    7171
    72 gdb.texi: gdb.t
     72gdb.texi: gdb.t versions.texi
    7373        $(BMENU) -c -p "Application executable" \
    7474            -u "Top" \
  • doc/started/buildc.t

    r9c2b087 rbdec2709  
    99@chapter Building the GNU C/C++ Cross Compiler Toolset
    1010
     11This chapter describes the steps required to acquire the
     12source code for a GNU cross compiler toolset, apply
     13any required RTEMS specific patches, compile that
     14toolset and install it.
     15
    1116@section Get all the pieces
    1217
    1318The tree structure in the figure below is assumed to be present in the
    1419following discussions:
     20
     21@center @b{XXX directory tree figure goes here}
    1522
    1623Gather the components that will be required for the installation and place
     
    1926approximately 20 megabytes.
    2027
    21 @example
    22 egcs 1.0.2
    23     FTP Site:    egcs.cygnus.com
    24     Directory:   /pub/egcs/releases/egcs-1.0.2
    25     File:        egcs-1.0.2-980309-prerelease.tar.gz
    26 
    27 binutils 2.8.1
    28     FTP Site:    ftp.gnu.org
    29     Directory:   /pub/gnu
    30     File:        binutils-2.8.1.tar.gz
    31 
    32 newlib 1.8.0
    33     FTP Site:    ftp.cygnus.com
    34     Directory:   /pub/newlib
    35     File:        newlib-1.8.0.tar.gz
    36 
    37 RTEMS @value{version}
    38 FTP Site:        ftp.oarcorp.com
    39     Directory:   /oarcorp/private/snapshots
    40     File:        rtems-980219.tgz
     28@subheading @value{GCC-VERSION}
     29@example
     30    FTP Site:    @value{GCC-FTPSITE}
     31    Directory:   @value{GCC-FTPDIR}
     32    File:        @value{GCC-TAR}
     33@end example
     34
     35@subheading @value{BINUTILS-VERSION}
     36@example
     37    FTP Site:    @value{BINUTILS-FTPSITE}
     38    Directory:   @value{BINUTILS-FTPDIR}
     39    File:        @value{BINUTILS-TAR}
     40@end example
     41
     42@subheading @value{NEWLIB-VERSION}
     43@example
     44    FTP Site:    @value{NEWLIB-FTPSITE}
     45    Directory:   @value{NEWLIB-FTPDIR}
     46    File:        @value{NEWLIB-TAR}
     47@end example
     48
     49@subheading @value{RTEMS-VERSION}
     50@example
     51    FTP Site:    @value{RTEMS-FTPSITE}
     52    Directory:   @value{RTEMS-FTPDIR}
     53    File:        @value{RTEMS-TAR}
    4154    File:        bit
    42     File:        binutils-2.8.1-rtems-diff-971221.gz
    43     File:        newlib-1.8.0-diff.980120.gz
    44     File:        simple_app.tgz
     55    File:        @value{BINUTILS-RTEMSPATCH}
     56    File:        @value{NEWLIB-RTEMSPATCH}
     57    File:        @value{GCC-RTEMSPATCH}
     58    File:        hello_world_c.tgz
    4559@end example
    4660
     
    5569@example
    5670cd tools
    57 tar xzf ../arc/egcs-1.0.2-980309-prerelease.tar.gz
    58 tar xzf ../arc/binutls-2.8.1.tar.gz
    59 tar xzf ../arc/newlib-1.8.0.tar.gz
     71tar xzf ../arc/@value{GCC-TAR}
     72tar xzf ../arc/@value{BINUTILS-TAR}
     73tar xzf ../arc/@value{NEWLIB-TAR}
    6074@end example
    6175
     
    6478
    6579@itemize @bullet
    66 @item binutils-2.8.1
    67 @item egcs-1.0.2
    68 @item newlib-1.8.0
     80@item @value{BINUTILS-UNTAR}
     81@item @value{GCC-UNTAR}
     82@item @value{NEWLIB-UNTAR}
    6983@end itemize
    7084
    71 @section Apply patches for newlib
    72 
    73 Apply the patches using the following command sequence:
    74 
    75 @example
    76 cd tools/newlib-1.8.0
    77 zcat arc/newlib-1.8.0-diff.980120.gz|patch -p1
     85@c
     86@c  EGCS patches
     87@c
     88
     89@section Apply RTEMS Patch to EGCS
     90
     91@ifclear GCC-RTEMSPATCH
     92No RTEMS specific patches are required for @value{GCC-VERSION} to
     93support @value{RTEMS-VERSION}.
     94@end ifclear
     95
     96@ifset GCC-RTEMSPATCH
     97
     98Apply the patch using the following command sequence:
     99
     100@example
     101cd tools/@value{GCC-UNTAR}
     102zcat arc/@value{GCC-RTEMSPATCH} | patch -p1
     103@end example
     104
     105Check to see if any of these patches have been rejected using the following
     106sequence:
     107
     108@example
     109cd tools/@value{GCC-UNTAR}
     110find . -name "*.rej" -print
     111@end example
     112
     113If any files are found with the .rej extension, a patch has been rejected.
     114This should not happen with a good patch file.
     115
     116To see the files that have been modified use the sequence:
     117
     118@example
     119cd tools/@value{GCC-UNTAR}
     120find . -name "*.orig" -print
     121@end example
     122
     123The files that are found, have been modified by the patch file.
     124
     125@end ifset
     126
     127@c
     128@c  BINUTILS patches
     129@c
     130
     131@section Apply RTEMS Patch to binutils
     132
     133@ifclear BINUTILS-RTEMSPATCH
     134No RTEMS specific patches are required for @value{BINUTILS-VERSION} to
     135support @value{RTEMS-VERSION}.
     136@end ifclear
     137
     138@ifset BINUTILS-RTEMSPATCH
     139Apply the patch using the following command sequence:
     140
     141@example
     142cd tools/@value{BINUTILS-UNTAR}
     143zcat arc/@value{BINUTILS-RTEMSPATCH} | patch -p1
    78144@end example
    79145
     
    82148
    83149@example
    84 cd tools/newlib-1.8.0
     150cd tools/@value{BINUTILS-UNTAR}
    85151find . -name "*.rej" -print
    86152@end example
     
    92158
    93159@example
    94 cd tools/newlib-1.8.0
     160cd tools/@value{BINUTILS-UNTAR}
    95161find . -name "*.orig" -print
    96162@end example
     
    98164The files that are found, have been modified by the patch file.
    99165
    100 
    101 @section Apply patches for binutils
    102 
    103 Apply the patches using the following command sequence:
    104 
    105 @example
    106 cd tools/binutils-2.8.1
    107 zcat arc/binutils-2.8.1-rtems-diff-971221.gz|patch -p1
     166@end ifset
     167
     168@c
     169@c  Newlib patches
     170@c
     171
     172@section Apply RTEMS Patch to newlib
     173
     174@ifclear NEWLIB-RTEMSPATCH
     175No RTEMS specific patches are required for @value{NEWLIB-VERSION} to
     176support @value{RTEMS-VERSION}.
     177@end ifclear
     178
     179@ifset NEWLIB-RTEMSPATCH
     180
     181Apply the patch using the following command sequence:
     182
     183@example
     184cd tools/@value{NEWLIB-UNTAR}
     185zcat arc/@value{NEWLIB-RTEMSPATCH} | patch -p1
    108186@end example
    109187
     
    112190
    113191@example
    114 cd tools/binutils-2.8.1
     192cd tools/@value{NEWLIB-UNTAR}
    115193find . -name "*.rej" -print
    116194@end example
     
    122200
    123201@example
    124 cd tools/binutils-2.8.1
     202cd tools/@value{NEWLIB-UNTAR}
    125203find . -name "*.orig" -print
    126204@end example
     
    128206The files that are found, have been modified by the patch file.
    129207
     208@end ifset
     209
     210@c
     211@c  Modify the bit script
     212@c
     213
    130214@section Modify the bit script
    131215
    132 Copy the bit file from arc to the tools directory.
    133 
    134 Edit the bit file to alter the following environmental variables:
     216Copy the @code{bit} script from arc to the tools directory.
     217
     218Edit the @code{bit} file to alter the following environmental variables:
    135219
    136220@itemize @bullet
     
    140224@item GCC
    141225@item BUILD_DOCS
     226@item BUILD_OTHER_LANGUAGES
    142227@end itemize
    143228
     
    157242#   GCC:          Newlib source directory
    158243#   BUILD_DOCS:   Set to "yes" if you want to install documentation.
     244#   BUILD_OTHER_LANGUAGES:
     245#                 Set to "yes" if you want to build Fortran and Objective-C
    159246#
    160 BINUTILS=gas-971208
    161 GCC=egcs-1.0.1
    162 NEWLIB=newlib-1.8.0
     247BINUTILS=@value{BINUTILS-UNTAR}
     248GCC=@value{GCC-UNTAR}
     249NEWLIB=@value{NEWLIB-UNTAR}
    163250BUILD_DOCS=yes
     251BUILD_OTHER_LANGUAGES=yes
    164252INSTALL_POINT=/home/joel/$@{GCC@}/$@{target@}
    165253
     
    167255@end example
    168256
    169 
    170 Where:
     257Where each of the variables which may be modified is described below:
    171258
    172259@table @code
     
    178265
    179266@item BINUTILS
    180 is the directory under tools that contains binutils-2.8.1.
    181 BINUTILS=binutils-2.8.1
     267is the directory under tools that contains @value{BINUTILS-UNTAR}.
     268For example,
     269
     270@example
     271BINUTILS=@value{BINUTILS-UNTAR}.
     272@end example
    182273
    183274@item GCC
    184 is the directory under tools that contains egcs-1.0.1.
    185 GCC=egcs-1.0.2-980309-prerelease
     275is the directory under tools that contains @value{GCC-UNTAR}.
     276For example,
     277
     278@example
     279GCC=@value{GCC-UNTAR}.
     280@end example
    186281
    187282@item NEWLIB
    188 is the directory under tools that contains newlib-1.8.0.
    189 NEWLIB=newlib-1.8.0
     283is the directory under tools that contains @value{NEWLIB-UNTAR}.
     284For example,
     285
     286@example
     287NEWLIB=@value{NEWLIB-UNTAR}.
     288@end example
    190289
    191290@item BUILD_DOCS
    192291is set to "yes" if you want to install documentation.
     292For example,
     293
     294@example
    193295BUILD_DOCS=yes
     296@end example
     297
     298@item BUILD_OTHER_LANGUAGES
     299is set to "yes" if you want to build languages other than C and C++.  At
     300the current time, this enables Fortan and Objective-C.
     301For example,
     302
     303@example
     304BUILD_OTHER_LANGUAGES=yes
     305@end example
    194306
    195307@end table
     
    197309@section Running the bit script
    198310
    199 Run the modified bit script using the following sequence:
     311After the @code{bit} script has been modified to reflect the
     312local installation, the modified @code{bit} script is run
     313using the following sequence:
    200314
    201315@example
     
    204318@end example
    205319
    206 Where:
    207 
    208 <target configuration> is one of the following:
    209 
    210 @example
    211 hppa1.1
    212 i386
    213 i386-elf
    214 i386-go32
    215 i960
    216 m68k
    217 mips64orion
    218 powerpc
    219 sh
    220 sparc
    221 @end example
    222 
    223 @section GNU C/C++ cross compiler toolset complete
    224  
    225 At this point the GNU C/C++ cross compile tools should be built.
    226 
     320Where <target configuration> is one of the following:
     321
     322@itemize @bullet
     323@item hppa1.1
     324@item i386
     325@item i386-elf
     326@item i386-go32
     327@item i960
     328@item m68k
     329@item mips64orion
     330@item powerpc
     331@item sh
     332@item sparc
     333@end itemize
     334
     335If no errors are encountered, the @code{bit} script will conclude by
     336printing messages similar to the following:
     337
     338@example
     339
     340The src and build-i386-tools subdirectory may now be removed.
     341
     342Started:  Fri Apr 10 10:14:07 CDT 1998
     343Finished: Fri Apr 10 12:01:33 CDT 1998
     344@end example
     345
     346If the @code{bit} script successfully completes, then the
     347GNU C/C++ cross compilation tools are installed.
     348
     349If the @code{bit} script does not successfully complete, then investigation
     350will be required to determine the source of the error.
     351
  • doc/started/buildrt.t

    r9c2b087 rbdec2709  
    1717@example
    1818cd tools
    19 tar xzf ../arc/rtems-980219.tgz
     19tar xzf ../arc/@value{RTEMS-TAR}
    2020@end example
    2121
    2222@section Add the bin directory under the install point to the default PATH
    2323
    24 Use the following command to append the <INSTALL_POINT>/bin directory to
    25 the PATH variable:
     24In order to compile RTEMS, you must have the cross compilation toolset
     25in your search patch.  The following command appends the directory
     26where the tools were installed in the previous chapter:
    2627
    2728@example
    28 PATH=$PATH:<INSTALL_POINT>/bin
     29export PATH=$PATH:<INSTALL_POINT>/bin
    2930@end example
     31
     32NOTE:  The above command is in Bourne shell (@code{sh}) syntax and should work with
     33the Korn (@code{ksh}) and GNU Bourne Again Shell (@code{bash}).  It will not
     34work with the C Shell (@code{csh})or derivatives of the C Shell.
    3035
    3136@section Generate RTEMS for a specific target and board support package
    3237
    3338Make a build directory under tools and build the RTEMS product in this
    34 directory. The ../rtems-980219/configure command has numerous command line
     39directory. The ../@value{RTEMS-UNTAR}/configure
     40command has numerous command line
    3541arguments. These arguments are discussed in detail in documentation that
    3642comes with the RTEMS distribution. In the installation described in the
    3743section "Unpack the RTEMS source", these configuration options can be found
    38 in file:
     44in file tools/@value{RTEMS-UNTAR}/README.configure.
    3945
    40 @example
    41 tools/rtems-980219/README.configure
    42 @end example
    43 
    44 A simple example of the configuration appears below:
     46The following shows the command sequence required to configure,
     47compile, and install RTEMS with the POSIX API, KA9Q TCP/IP,
     48and C++ support disabled.  RTEMS will be built to target
     49the @code{BOARD_SUPPORT_PACKAGE} board.
    4550
    4651@example
    4752mkdir build-rtems
    4853cd build-rtems
    49 ../rtems-980219/configure --target=<TARGET_CONFIGURATION> \
    50 --disable-posix --disable-ka9q --disable-cpp \
    51 --enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\
    52 --prefix=< INSTALL_POINT>
     54../@value{RTEMS-UNTAR}/configure --target=<TARGET_CONFIGURATION> \
     55    --disable-posix --disable-ka9q --disable-cxx \
     56    --enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\
     57    --prefix=<INSTALL_POINT>
    5358gmake all install
    5459@end example
     
    5661Where:
    5762
    58 The current summary of <TARGET_CONFIGURATION>'s and
     63The list of currently supported of <TARGET_CONFIGURATION>'s and
    5964<BOARD_SUPPORT_PACKAGE>'s can be found in
    60 tools/rtems-980219/README.configure
    61 
     65tools/@value{RTEMS-UNTAR}/README.configure.
    6266
    6367<INSTALL_POINT> is the installation point from the previous step
  • doc/started/gdb.t

    r9c2b087 rbdec2709  
    1010
    1111GDB is not currently RTEMS aware. The following configurations have been
    12 successfully used with RTEMS applications.
     12successfully used with RTEMS applications:
    1313
    14 @section GDB with Sparc Instruction Simulation (SIS)
     14@itemize bullet
     15@item Sparc Instruction Simulator (SIS)
     16@item PowerPC Instruction Simulator (PSIM)
     17@item DINK32
     18@end itemize
    1519
    16 @subsection Unarchive the gdb distribution (SIS)
     20Other configurations of gdb have successfully been used by RTEMS users
     21but are not documented here.
     22
     23@section Unarchive the gdb distribution
    1724
    1825Use the following commands to unarchive the gdb distribution:
     
    2027@example
    2128cd tools
    22 tar xzf ../arc/gdb-980122.tar.gz
     29tar xzf ../arc/@value{GDB-TAR}
    2330@end example
    2431
    25 The directory gdb-980122 is created under the tools directory.
     32@c
     33@c  GDB Patch
     34@c
    2635
    27 @subsection Make the build directory (SIS)
     36@section Apply RTEMS Patch to GDB
     37
     38@ifclear GDB-RTEMSPATCH
     39No RTEMS specific patches are required for @value{GDB-VERSION} to
     40support @value{RTEMS-VERSION}.
     41@end ifclear
     42
     43@ifset GDB-RTEMSPATCH
     44
     45Apply the patch using the following command sequence:
     46
     47@example
     48cd tools/@value{GDB-UNTAR}
     49zcat arc/@value{GDB-RTEMSPATCH} | patch -p1
     50@end example
     51
     52Check to see if any of these patches have been rejected using the following
     53sequence:
     54
     55@example
     56cd tools/@value{GDB-UNTAR}
     57find . -name "*.rej" -print
     58@end example
     59
     60If any files are found with the .rej extension, a patch has been rejected.
     61This should not happen with a good patch file.
     62
     63To see the files that have been modified use the sequence:
     64
     65@example
     66cd tools/@value{GDB-UNTAR}
     67find . -name "*.orig" -print
     68@end example
     69
     70The files that are found, have been modified by the patch file.
     71
     72@end ifset
     73
     74
     75@section GDB with Sparc Instruction Simulation (SIS)
     76
     77The directory @value{GDB-UNTAR} is created under the tools directory.
     78
     79@subheading Make the build directory
    2880
    2981Create a build directory for the SIS Debugger
     
    3486@end example
    3587
    36 @subsection Configure for the build (SIS)
     88@subheading Configure for the build
    3789
    38 Configure the general gdb distribution for Sparc Instruction Simulation
     90Configure the GNU Debugger for the
     91Sparc Instruction Simulator (SIS):
    3992
    4093@example
    4194cd tools/build-sis
    42 ../gdb-980122/configure --target-sparc-erc32-aout \
    43 --program-prefix=sparc-rtems- \
    44 --disable-gdbtk \
    45 --with-targets=all \
    46 --prefix=<INSTALL_POINT_FOR_SIS>
     95../@value{GDB-UNTAR}/configure --target-sparc-erc32-aout \
     96    --program-prefix=sparc-rtems- \
     97    --disable-gdbtk \
     98    --enable-targets=all \
     99    --prefix=<INSTALL_POINT_FOR_SIS>
    47100@end example
    48101
    49 Where:
     102Where <INSTALL_POINT_FOR_SIS> is a unique location where the gdb
     103with SIS will be created.
    50104
    51 <INSTALL_POINT_FOR_SIS> is a unique location where the gdb with SIS will be
    52 created.
     105@subheading Make the debugger
    53106
    54 @subsection Make the debugger (SIS)
    55 
    56 From tools/build-sis run:
     107From tools/build-sis execute the following command sequence:
    57108
    58109@example
    59 gmake
     110gmake all install
    60111@end example
    61112
    62113
    63 @section GDB with PowerPC Instruction Simulator (PSIM)
     114@section GDB with PowerPC Instruction Simulator
    64115
    65 @subsection Unarchive the gdb distribution (PSIM)
    66 
    67 Use the following commands to unarchive the gdb distribution:
    68 
    69 @example
    70 cd tools
    71 tar xzf ../arc/gdb-980122.tar.gz
    72 @end example
    73 
    74 The directory gdb-980122 is created under the tools directory.
    75 
    76 
    77 @subsection Make the build directory (PSIM)
     116@subheading Make the build directory
    78117
    79118Create a build directory for the SIS Debugger
     
    84123@end example
    85124
    86 @subsection Configure for the build
     125@subheading Configure for the build
    87126
    88 Configure the general gdb distribution for PowerPC Instruction Simulation
     127Configure the GNU Debugger for the PowerPC
     128Instruction Simulator (PSIM):
    89129
    90130@example
    91131cd tools/build-ppc
    92 ../gdb-980122/configure --host=i486-linux \
     132../@value{GDB-UNTAR}/configure \
    93133      --target=powerpc-unknown-eabi \
    94134      --program-prefix=powerpc-rtems- \
     
    97137      --enable-sim-inline \
    98138      --enable-sim-hardware \
    99 --prefix=<INSTALL_POINT_FOR_PPC>
     139      --enable-targets=all \
     140      --prefix=<INSTALL_POINT_FOR_PPC>
    100141@end example
    101142
    102 Where:
    103 
    104 <INSTALL_POINT_FOR_PPC> is a unique location where the gdb with PSIM will
    105 be created.
     143Where <INSTALL_POINT_FOR_PPC> is a unique location where the gdb
     144with PSIM will be created.
    106145
    107146
    108 @subsection Make the debugger (PSIM)
     147@subheading Make the debugger
    109148
    110 From tools/build-ppc run:
     149From tools/build-ppc execute the following command sequence:
    111150
    112151@example
    113 gmake
     152gmake all install
    114153@end example
    115154
     
    117156@section GDB with Dink32
    118157
    119 @subsection Unarchive the gdb distribution (DINK32)
     158@subheading Unarchive the gdb distribution
    120159
    121160Use the following commands to unarchive the gdb distribution:
    122161
    123 @example
    124 cd tools
    125 tar xzf ../arc/gdb-980122.tar.gz
    126 @end example
    127 
    128 The directory gdb-980122 is created under the tools directory.
    129 
    130 
    131 @subsection Make the build directory (DINK32)
     162@subheading Make the build directory
    132163
    133164Create a build directory for the DINK32 Debugger
     
    138169@end example
    139170
    140 @subsection Replace dink32-rom.c
     171@subheading Configure for the build
    141172
    142 Obtain a valid copy of dink32-rom.c from RTEMS site.
    143 
    144 Replace the copy of dink32-rom.c that came with the gdb-980122
    145 distribution. It is located in:
    146 
    147 @example
    148 tools/gdb-980122/gdb/dink32-rom.c
    149 @end example
    150 
    151 
    152 @subsection Configure for the build (DINK32)
    153 
    154 Configure the general gdb distribution for Sparc Instruction Simulation
     173Configure the GNU Debugger to communicate with
     174the DINK32 ROM monitor:
    155175
    156176@example
    157177cd tools/build-dink32
    158 ../gdb-980122/configure --target-powerpc-elf \
    159 --program-prefix=powerpc-rtems- \
    160 --prefix=<INSTALL_POINT_FOR_DINK32>
    161 --with-targets=all \
     178../@value{GDB-UNTAR}/configure --target-powerpc-elf \
     179    --program-prefix=powerpc-rtems- \
     180    --enable-targets=all \
     181    --prefix=<INSTALL_POINT_FOR_DINK32>
    162182@end example
    163183
    164 Where:
     184Where <INSTALL_POINT_FOR_DINK32> is a unique location where the
     185gdb Dink32 will be created.
    165186
    166 <INSTALL_POINT_FOR_DINK32> is a unique location where the gdb Dink32 will
    167 be created.
     187@subheading Make the debugger
    168188
    169 @subsection Make the debugger (DINK32)
    170 
    171 From tools/build-dink32 run:
     189From tools/build-dink32 execute the following command sequence:
    172190
    173191@example
    174 gmake
     192gmake all install
    175193@end example
    176194
  • doc/started/intro.t

    r9c2b087 rbdec2709  
    88
    99@chapter Introduction
     10
     11The purpose of this document is to guide you through the process of
     12installing a GNU cross development environment to use with RTEMS.
    1013
    1114If you are already familiar with the concepts behind a cross compiler and
  • doc/started/require.t

    r9c2b087 rbdec2709  
    2424@end example
    2525
     26The instructions in this manual should work on any computer running
     27a UNIX variant.  Some native GNU tools are used by this procedure
     28including:
     29
     30@itemize @bullet
     31@item GCC
     32@item GNU make
     33@end itemize
     34
     35In addition, some native utilities may be deficient for building
     36the GNU tools.
  • doc/started/sample.t

    r9c2b087 rbdec2709  
    1515@example
    1616cd tools
    17 tar xzf ../arc/simple_app.tgz
     17tar xzf ../arc/hello_world_c.tgz
    1818@end example
    1919
     
    3030Where:
    3131
    32 <INSTALLATION_POINT> and <BOARD_SUPPORT_PACKAGE> are those used in step 4.3
     32<INSTALLATION_POINT> and <BOARD_SUPPORT_PACKAGE> are those used when
     33configuring and installing RTEMS.
    3334
    3435@section Build the Sample Application
     
    3738
    3839@example
    39 cd tools/simple_app
     40cd tools/hello_world_c
    4041gmake
    4142@end example
     
    4344If no errors are detected during the sample application build, it is
    4445reasonable to assume that the build of the GNU C/C++ Cross Compiler Tools
    45 for RTEMS and the build of the RTEMS OS for the selected host and target
     46for RTEMS and RTEMS itself for the selected host and target
    4647combination was done properly.
    4748
    4849@section Application executable
    4950
    50 If the application build has taken place without error, the application
     51If the sample application has successfully been build, then the application
    5152executable is placed in the following directory:
    5253
     
    5556@end example
    5657
     58How this executable is downloaded to the target board is very dependent
     59on the BOARD_SUPPORT_PACKAGE selected.
  • doc/started/started.texi

    r9c2b087 rbdec2709  
    2222@include ../common/setup.texi
    2323
     24@c
     25@c  Now set all the tool version dependent information
     26@c
     27@include versions.texi
     28
    2429@ignore
    2530@ifinfo
    2631@format
    2732START-INFO-DIR-ENTRY
    28 * RTEMS Getting Started Guide (started):
     33* Getting Started with RTEMS for C/C++ Users (started):
    2934END-INFO-DIR-ENTRY
    3035@end format
     
    4752
    4853@setchapternewpage odd
    49 @settitle Getting Started with RTEMS
     54@settitle Getting Started with RTEMS for C/C++ Users
    5055@titlepage
    5156@finalout
    5257
    53 @title Getting Started with RTEMS
     58@title Getting Started with RTEMS for C/C++ Users
    5459@subtitle Edition @value{edition}, for RTEMS @value{version}
    5560@sp 1
     
    7479@top started
    7580
    76 This is the online version of the Getting Started with RTEMS for C/C++
    77 Developers.
     81This is the online version of the Getting Started with RTEMS for C/C++ Users.
    7882
    7983@menu
Note: See TracChangeset for help on using the changeset viewer.