RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

"arc" changed to "archive"

Browse Source 
Pictures now in ASCII.
This commit is contained in:
Joel Sherrill
1998-04-14 21:17:53 +00:00
parent 3b89891244
commit ae2e9f2935
5 changed files with 68 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files

135
doc/started/buildc.t
View File

@@ -21,50 +21,28 @@ directory. The command sequence to do this is shown
below: below:
@example @example
mkdir arc mkdir archive
mkdir tools mkdir tools
@end example @end example
This will result in an initial directory structure similar to the This will result in an initial directory structure similar to the
one shown in the following figure: one shown in the following figure:
@ifset use-ascii
@example @example
@group @group
parent directory common to the /whatever/prefix/you/choose/
tools and archive subdirectories archive/
| tools/
+----------------------+----------------------+
| |
tools arc
@end group @end group
@end example @end example
@end ifset
@c @ifset use-html
@ifset use-tex @c @html
@c for now use the ascii version @c <IMG SRC="sfile12c.jpg" WIDTH=417 HEIGHT=178
@example @c ALT="Starting Directory Organization">
@group @c @end html
parent directory common to the @c @end ifset
tools and archive subdirectories
|
+----------------------+----------------------+
| |
tools arc
@end group
@end example
@tex
@end tex
@end ifset
@ifset use-html
@html
<IMG SRC="sfile12c.jpg" WIDTH=417 HEIGHT=178
ALT="Starting Directory Organization">
@end html
@end ifset
@section Get All the Pieces @section Get All the Pieces
@@ -148,9 +126,9 @@ tar files using the following command sequence:
@example @example
cd tools cd tools
tar xzf ../arc/@value{GCC-TAR} tar xzf ../archive/@value{GCC-TAR}
tar xzf ../arc/@value{BINUTILS-TAR} tar xzf ../archive/@value{BINUTILS-TAR}
tar xzf ../arc/@value{NEWLIB-TAR} tar xzf ../archive/@value{NEWLIB-TAR}
@end example @end example
After the compressed tar files have been unpacked, the following After the compressed tar files have been unpacked, the following
@@ -162,51 +140,64 @@ directories will have been created under tools.
@item @value{NEWLIB-UNTAR} @item @value{NEWLIB-UNTAR}
@end itemize @end itemize
The @code{bit} script will automatically create two other Copy the @code{bit} script from the @code{archive} directory
subdirectories: to the @code{tools} directory as shown below:
@example
cp ../archive/bit .
@end example
When the @code{bit} script is executed later in this process,
it will automatically create two other subdirectories:
@itemize @bullet @itemize @bullet
@item src @item src
@item build-$@{CPU@}-tools @item build-$@{CPU@}-tools
@end itemize @end itemize
Ignoring version numbers, this will look something like the following figure: @itemize @bullet
@item src
@item build-$@{CPU@}-tools
@end itemize
The tree should look something like the following figure:
@ifset use-ascii
@example @example
@group @group
tools /whatever/prefix/you/choose/
| bit (script) bit
+ archive/
+---------+-------------+------------+----------------+ @value{GCC-TAR}
| | | | | @value{BINUTILS-TAR}
src binutils-2.9 egcs-1.0.2 newlib-1.8.0 build-$@{CPU@}-tools @value{NEWLIB-TAR}
@value{RTEMS-TAR}
@ifset GCC-RTEMSPATCH
@value{GCC-RTEMSPATCH}
@end ifset
@ifset BINUTILS-RTEMSPATCH
@value{BINUTILS-RTEMSPATCH}
@end ifset
@ifset NEWLIB-RTEMSPATCH
@value{NEWLIB-RTEMSPATCH}
@end ifset
hello_world_c.tgz
bit
tools/
@value{BINUTILS-UNTAR}/
@value{GCC-UNTAR}/
@value{NEWLIB-UNTAR}/
@value{RTEMS-UNTAR}/
bit
@end group @end group
@end example @end example
@end ifset
@ifset use-tex @c @ifset use-html
@c for now use the ascii version @c @html
@example @c <IMG SRC="bit_c.jpg" WIDTH=816 HEIGHT=267 ALT="Directory Organization">
@group @c @end html
tools @c @end ifset
| bit (script)
+
+---------+-------------+------------+----------------+
| | | | |
src binutils-2.9 egcs-1.0.2 newlib-1.8.0 build-${CPU}-tools
@end group
@end example
@tex
@end tex
@end ifset
@ifset use-html
@html
<IMG SRC="bit_c.jpg" WIDTH=816 HEIGHT=267 ALT="Directory Organization">
@end html
@end ifset
@c @c
@c Reading the Documentation @c Reading the Documentation
@@ -235,7 +226,7 @@ Apply the patch using the following command sequence:
@example @example
cd tools/@value{GCC-UNTAR} cd tools/@value{GCC-UNTAR}
zcat arc/@value{GCC-RTEMSPATCH} | patch -p1 zcat archive/@value{GCC-RTEMSPATCH} | patch -p1
@end example @end example
Check to see if any of these patches have been rejected using the following Check to see if any of these patches have been rejected using the following
@@ -267,7 +258,7 @@ Apply the patch using the following command sequence:
@example @example
cd tools/@value{BINUTILS-UNTAR} cd tools/@value{BINUTILS-UNTAR}
zcat arc/@value{BINUTILS-RTEMSPATCH} | patch -p1 zcat archive/@value{BINUTILS-RTEMSPATCH} | patch -p1
@end example @end example
Check to see if any of these patches have been rejected using the following Check to see if any of these patches have been rejected using the following
@@ -300,7 +291,7 @@ Apply the patch using the following command sequence:
@example @example
cd tools/@value{NEWLIB-UNTAR} cd tools/@value{NEWLIB-UNTAR}
zcat arc/@value{NEWLIB-RTEMSPATCH} | patch -p1 zcat archive/@value{NEWLIB-RTEMSPATCH} | patch -p1
@end example @end example
Check to see if any of these patches have been rejected using the following Check to see if any of these patches have been rejected using the following
@@ -322,7 +313,7 @@ This should not happen with a good patch file.
@section Modify the bit Script @section Modify the bit Script
Copy the @code{bit} script from arc to the tools directory. Copy the @code{bit} script from @code{archive} to the tools directory.
Edit the @code{bit} file to alter the following environmental variables: Edit the @code{bit} file to alter the following environmental variables:

2
doc/started/buildrt.t
View File

@@ -16,7 +16,7 @@ tools directory:
@example @example
cd tools cd tools
tar xzf ../arc/@value{RTEMS-TAR} tar xzf ../archive/@value{RTEMS-TAR}
@end example @end example
@section Add <INSTALL_POINT>/bin to Executable PATH @section Add <INSTALL_POINT>/bin to Executable PATH

4
doc/started/gdb.t
View File

@@ -26,7 +26,7 @@ Use the following commands to unarchive the gdb distribution:
@example @example
cd tools cd tools
tar xzf ../arc/@value{GDB-TAR} tar xzf ../archive/@value{GDB-TAR}
@end example @end example
The directory @value{GDB-UNTAR} is created under the tools directory. The directory @value{GDB-UNTAR} is created under the tools directory.
@@ -48,7 +48,7 @@ Apply the patch using the following command sequence:
@example @example
cd tools/@value{GDB-UNTAR} cd tools/@value{GDB-UNTAR}
zcat arc/@value{GDB-RTEMSPATCH} | patch -p1 zcat archive/@value{GDB-RTEMSPATCH} | patch -p1
@end example @end example
Check to see if any of these patches have been rejected using the following Check to see if any of these patches have been rejected using the following

2
doc/started/require.t
View File

@@ -16,7 +16,7 @@ assessing the amount of disk space required for your installation:
+----------------------------------------+------------------------------+ +----------------------------------------+------------------------------+
| Component | Disk Space Required | | Component | Disk Space Required |
+----------------------------------------+------------------------------+ +----------------------------------------+------------------------------+
| arc directory | 20 Mbytes | | archive directory | 20 Mbytes |
| tools src unzipped | 77 Mbytes | | tools src unzipped | 77 Mbytes |
| each individual build directory | 120 Mbytes worst case | | each individual build directory | 120 Mbytes worst case |
| each installation directory | 20-60 Mbytes | | each installation directory | 20-60 Mbytes |

2
doc/started/sample.t
View File

@@ -14,7 +14,7 @@ Use the following command to unarchive the sample application:
@example @example
cd tools cd tools
tar xzf ../arc/hello_world_c.tgz tar xzf ../archive/hello_world_c.tgz
@end example @end example
@section Set the Environment Variable RTEMS_MAKEFILE_PATH @section Set the Environment Variable RTEMS_MAKEFILE_PATH