Imagelibrary/rtems
1
0
Fork 1
mirror of https://gitlab.rtems.org/rtems/rtos/rtems.git synced 2025-12-09 09:03:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

2004-09-27 Joel Sherrill <joel@OARcorp.com>

Browse Source 
PR 681/doc
	PR 682/doc
	* buildc.t, buildrt.t, sample.t: Fix PATH and tar examples. Enable
	binutils link again.
	* user/overview.t: Chapter numbering in preface was wrong.
This commit is contained in:
Joel Sherrill
2004-09-27 22:28:16 +00:00
parent 7a965bcd6a
commit 34ffa99630
5 changed files with 44 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/ChangeLog
View File

@@ -1,3 +1,11 @@
2004-09-27 Joel Sherrill <joel@OARcorp.com>
PR 681/doc
PR 682/doc
* buildc.t, buildrt.t, sample.t: Fix PATH and tar examples. Enable
binutils link again.
* user/overview.t: Chapter numbering in preface was wrong.
2004-09-24 Ralf Corsepius <ralf_corsepius@rtems.org> 2004-09-24 Ralf Corsepius <ralf_corsepius@rtems.org>
* configure.ac: Require automake > 1.9. * configure.ac: Require automake > 1.9.

5
doc/started/buildc.t
View File

@@ -498,11 +498,12 @@ invoke the @value{BINUTILSUNTAR} @code{configure} command with the
@code{--help} option. @code{--help} option.
NOTE: The shell PATH variable needs to be updated to include the path NOTE: The shell PATH variable needs to be updated to include the path
the binutils has been installed in. This the prefix used above with the binutils user executables have been installed in. The directory
containing the executables is the prefix used above with
@file{bin} post-fixed. @file{bin} post-fixed.
@example @example
export PATH=$PATH:@value{RTEMSPREFIX}/bin export PATH=@value{RTEMSPREFIX}/bin:${PATH}
@end example @end example
Failure to have the binutils in the path will cause the GCC and NEWLIB Failure to have the binutils in the path will cause the GCC and NEWLIB

13
doc/started/buildrt.t
View File

@@ -20,10 +20,7 @@ placed in your @code{archive} directory.
FTP Site: @value{RTEMSFTPSITE} FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMSFTPDIR}/@value{VERSION} Directory: @value{RTEMSFTPDIR}/@value{VERSION}
File: @value{RTEMSTAR} File: @value{RTEMSTAR}
@ifset use-html URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}/@value{RTEMSTAR},,ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}/@value{RTEMSTAR}}
@c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}, Download RTEMS components}
URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}
@end ifset
@end example @end example
@subheading RTEMS Examples including Hello World @subheading RTEMS Examples including Hello World
@@ -54,11 +51,13 @@ This creates the directory @value{RTEMSUNTAR}.
@section Add <INSTALL_POINT>/bin to Executable PATH @section Add <INSTALL_POINT>/bin to Executable PATH
In order to compile RTEMS, you must have the cross compilation toolset In order to compile RTEMS, you must have the cross compilation toolset
in your search path. The following command appends the directory in your search path. It is important to have the RTEMS toolset first
where the tools were installed prior to this point: in your path to ensure that you are using the intended version of all
tools. The following command prepends the directory
where the tools were installed in a previous step:
@example @example
export PATH=$PATH:<INSTALL_POINT>/bin export PATH=<INSTALL_POINT>/bin:${PATH}
@end example @end example
NOTE: The above command is in Bourne shell (@code{sh}) syntax and NOTE: The above command is in Bourne shell (@code{sh}) syntax and

2
doc/started/sample.t
View File

@@ -210,7 +210,7 @@ applications:
@example @example
cd tools cd tools
tar xzf ../archive/hello_world_ada.tgz tar xjf ../archive/ada-examples-@value{VERSION}.tar.bz2
@end example @end example
@subheading Create a BSP Specific Makefile @subheading Create a BSP Specific Makefile

48
doc/user/overview.t
View File

@@ -434,97 +434,101 @@ introduction to the ideas which are common across multiple RTEMS
managers. managers.
@item Chapter 3: @item Chapter 3:
RTEMS Data Types: describes the fundamental data types shared
by the services in the RTEMS Classic API.
@item Chapter 4:
Initialization Manager: describes the functionality and directives Initialization Manager: describes the functionality and directives
provided by the Initialization Manager. provided by the Initialization Manager.
@item Chapter 4: @item Chapter 5:
Task Manager: describes the functionality and directives provided Task Manager: describes the functionality and directives provided
by the Task Manager. by the Task Manager.
@item Chapter 5: @item Chapter 6:
Interrupt Manager: describes the functionality and directives Interrupt Manager: describes the functionality and directives
provided by the Interrupt Manager. provided by the Interrupt Manager.
@item Chapter 6: @item Chapter 7:
Clock Manager: describes the functionality and directives Clock Manager: describes the functionality and directives
provided by the Clock Manager. provided by the Clock Manager.
@item Chapter 7 @item Chapter 8:
Timer Manager: describes the functionality and directives provided Timer Manager: describes the functionality and directives provided
by the Timer Manager. by the Timer Manager.
@item Chapter 8: @item Chapter 9:
Semaphore Manager: describes the functionality and directives Semaphore Manager: describes the functionality and directives
provided by the Semaphore Manager. provided by the Semaphore Manager.
@item Chapter 9: @item Chapter 10:
Message Manager: describes the functionality and directives Message Manager: describes the functionality and directives
provided by the Message Manager. provided by the Message Manager.
@item Chapter 10: @item Chapter 11:
Event Manager: describes the Event Manager: describes the
functionality and directives provided by the Event Manager. functionality and directives provided by the Event Manager.
@item Chapter 11: @item Chapter 12:
Signal Manager: describes the Signal Manager: describes the
functionality and directives provided by the Signal Manager. functionality and directives provided by the Signal Manager.
@item Chapter 12: @item Chapter 13:
Partition Manager: describes the Partition Manager: describes the
functionality and directives provided by the Partition Manager. functionality and directives provided by the Partition Manager.
@item Chapter 13: @item Chapter 14:
Region Manager: describes the Region Manager: describes the
functionality and directives provided by the Region Manager. functionality and directives provided by the Region Manager.
@item Chapter 14: @item Chapter 15:
Dual-Ported Memory Manager: describes Dual-Ported Memory Manager: describes
the functionality and directives provided by the Dual-Ported the functionality and directives provided by the Dual-Ported
Memory Manager. Memory Manager.
@item Chapter 15: @item Chapter 16:
I/O Manager: describes the I/O Manager: describes the
functionality and directives provided by the I/O Manager. functionality and directives provided by the I/O Manager.
@item Chapter 16: @item Chapter 17:
Fatal Error Manager: describes the functionality and directives Fatal Error Manager: describes the functionality and directives
provided by the Fatal Error Manager. provided by the Fatal Error Manager.
@item Chapter 17: @item Chapter 18:
Scheduling Concepts: details the RTEMS scheduling algorithm and Scheduling Concepts: details the RTEMS scheduling algorithm and
task state transitions. task state transitions.
@item Chapter 18: @item Chapter 19:
Rate Monotonic Manager: describes the functionality and directives Rate Monotonic Manager: describes the functionality and directives
provided by the Rate Monotonic Manager. provided by the Rate Monotonic Manager.
@item Chapter 19: @item Chapter 20:
Board Support Packages: defines the Board Support Packages: defines the
functionality required of user-supplied board support packages. functionality required of user-supplied board support packages.
@item Chapter 20: @item Chapter 21:
User Extensions: shows the user how to User Extensions: shows the user how to
extend RTEMS to incorporate custom features. extend RTEMS to incorporate custom features.
@item Chapter 21: @item Chapter 22:
Configuring a System: details the process by which one tailors RTEMS Configuring a System: details the process by which one tailors RTEMS
for a particular single-processor or multiprocessor application. for a particular single-processor or multiprocessor application.
@item Chapter 22: @item Chapter 23:
Multiprocessing Manager: presents a Multiprocessing Manager: presents a
conceptual overview of the multiprocessing capabilities provided conceptual overview of the multiprocessing capabilities provided
by RTEMS as well as describing the Multiprocessing by RTEMS as well as describing the Multiprocessing
Communications Interface Layer and Multiprocessing Manager Communications Interface Layer and Multiprocessing Manager
directives. directives.
@item Chapter 23: @item Chapter 24:
Directive Status Codes: provides a definition of each of the Directive Status Codes: provides a definition of each of the
directive status codes referenced in this manual. directive status codes referenced in this manual.
@item Chapter 24: @item Chapter 25:
Example Application: provides a template for simple RTEMS applications. Example Application: provides a template for simple RTEMS applications.
@item Chapter 25: @item Chapter 26:
Glossary: defines terms used throughout this manual. Glossary: defines terms used throughout this manual.
@end table @end table