mirror of
https://gitlab.rtems.org/rtems/rtos/rtems.git
synced 2026-11-09 08:37:58 +08:00
2010-12-14 Joel Sherrill <joel.sherrill@oarcorp.com>
* Makefile.am, configure.ac, common/cpright.texi, common/rtems.texi.in, cpu_supplement/.cvsignore, started/Makefile.am, started/binaries.t, started/buildc.t, started/buildrt.t, started/intro.t, started/nextstep.t, started/nt.t, started/require.t, started/sample.t, started/started.texi, started/version.texi: Major update which includes removal of references to specific tool versions and patches. * started/tversions.texi.in: Removed.
This commit is contained in:
Joel Sherrill committed
1 parent
8e03eb3fd0
commit
df6311707e
18 files changed
+1012
-1229
No files matched your search
@@ -1,3 +1,14 @@
|
||||
2010-12-14 Joel Sherrill <joel.sherrill@oarcorp.com>
|
||||
|
||||
* Makefile.am, configure.ac, common/cpright.texi, common/rtems.texi.in,
|
||||
cpu_supplement/.cvsignore, started/Makefile.am, started/binaries.t,
|
||||
started/buildc.t, started/buildrt.t, started/intro.t,
|
||||
started/nextstep.t, started/nt.t, started/require.t,
|
||||
started/sample.t, started/started.texi, started/version.texi: Major
|
||||
update which includes removal of references to specific tool versions
|
||||
and patches.
|
||||
* started/tversions.texi.in: Removed.
|
||||
|
||||
2010-11-24 Gedare Bloom <giddyup44@yahoo.com>
|
||||
|
||||
PR 1647/cpukit
|
||||
|
||||
+1
-1
@@ -8,7 +8,7 @@ ACLOCAL_AMFLAGS = -I ../aclocal
|
||||
# + tools, common and images are shared across many documents
|
||||
|
||||
SUBDIRS = tools started user bsp_howto porting develenv posix_users \
|
||||
posix1003.1 filesystem networking ada_user started_ada \
|
||||
posix1003.1 filesystem networking ada_user \
|
||||
new_chapters relnotes cpu_supplement shell
|
||||
|
||||
if USE_HTML
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2008.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -17,7 +17,7 @@
|
||||
@end tex
|
||||
|
||||
@vskip 0pt plus 1filll
|
||||
COPYRIGHT @copyright{} 1988 - 2008.@*
|
||||
COPYRIGHT @copyright{} 1988 - 2010.@*
|
||||
On-Line Applications Research Corporation (OAR).@*
|
||||
|
||||
The authors have used their best efforts in preparing
|
||||
@@ -36,5 +36,5 @@ Any inquiries concerning RTEMS, its related support
|
||||
components, its documentation, or any custom services
|
||||
for RTEMS should be directed to the contacts listed on
|
||||
that site. A current list of RTEMS Support Providers
|
||||
is at @uref{http://www.rtems.com/support.html}.
|
||||
is at @uref{http://www.rtems.com/oarsupport}.
|
||||
|
||||
@@ -11,4 +11,3 @@
|
||||
@set RTEMSPREFIX @RTEMSPREFIX@
|
||||
@set RTEMSAPI @RTEMSAPI@
|
||||
@set RTEMSRPMPREFIX @RTEMSRPMPREFIX@
|
||||
@set RTEMSRPMGROUP @RTEMSRPMGROUP@
|
||||
+1
-45
@@ -137,30 +137,6 @@ dnl Checks for typedefs, structures, and compiler characteristics.
|
||||
|
||||
dnl Checks for library functions.
|
||||
|
||||
AC_MSG_CHECKING([for ./setup.def])
|
||||
AS_IF([test -f ${srcdir}/setup.def],[
|
||||
. ${srcdir}/setup.def
|
||||
AC_MSG_RESULT([done])
|
||||
],[
|
||||
AC_MSG_ERROR([missing])
|
||||
])
|
||||
|
||||
AS_IF([test -z "$binutils_patch_version"],
|
||||
[set_binutils_patch="@clear BINUTILSPATCHVERSION"],
|
||||
[set_binutils_patch="@set BINUTILSPATCHVERSION $binutils_patch_version"])
|
||||
|
||||
AS_IF([test -z "$newlib_patch_version"],
|
||||
[set_newlib_patch="@clear NEWLIBPATCHVERSION"],
|
||||
[set_newlib_patch="@set NEWLIBPATCHVERSION $newlib_patch_version"])
|
||||
|
||||
AS_IF([test -z "$gcc_patch_version"],
|
||||
[set_gcc_patch="@clear GCCPATCHVERSION"],
|
||||
[set_gcc_patch="@set GCCPATCHVERSION $gcc_patch_version"])
|
||||
|
||||
AS_IF([test -z "$gdb_patch_version"],
|
||||
[set_gdb_patch="@clear GDBPATCHVERSION"],
|
||||
[set_gdb_patch="@set GDBPATCHVERSION $gdb_patch_version"])
|
||||
|
||||
AC_CONFIG_SUBDIRS(tools)
|
||||
|
||||
AC_CONFIG_FILES([Makefile],[],[
|
||||
@@ -170,7 +146,6 @@ cat << EOF > common/rtems.sed~
|
||||
s/@RTEMSAPI@/RTEMS_API/;t t
|
||||
s,@RTEMSPREFIX@,$prefix,;t t
|
||||
s,@RTEMSRPMPREFIX@,$rpmprefix,;t t
|
||||
s,@RTEMSRPMGROUP@,RTEMS/]RTEMS_API[,;t t
|
||||
EOF
|
||||
_RTEMS_UPDATE_CONDITIONAL([common/rtems.sed],[common/rtems.sed~])
|
||||
])
|
||||
@@ -181,25 +156,6 @@ develenv/Makefile
|
||||
user/Makefile
|
||||
bsp_howto/Makefile])
|
||||
|
||||
AC_CONFIG_FILES([started/Makefile],[],[
|
||||
test -d started || mkdir started
|
||||
cat << EOF > started/tversions.sed~
|
||||
:t
|
||||
s/@GCCVERSION@/$gcc_version/;t t
|
||||
s/@BINUTILSVERSION@/$binutils_version/;t t
|
||||
s/@NEWLIBVERSION@/$newlib_version/;t t
|
||||
s/@GDBVERSION@/$gdb_version/;t t
|
||||
s/@SETBINUTILSPATCHVERSION@/$set_binutils_patch/;t t
|
||||
s/@SETGCCPATCHVERSION@/$set_gcc_patch/;t t
|
||||
s/@SETNEWLIBPATCHVERSION@/$set_newlib_patch/;t t
|
||||
s/@SETGDBPATCHVERSION@/$set_gdb_patch/;t t
|
||||
s/@GCCRPMRELEASE@/$gccnewlib_rpm_release/;t t
|
||||
s/@BINUTILSRPMRELEASE@/$binutils_rpm_release/;t t
|
||||
s/@GDBRPMRELEASE@/$gdb_rpm_release/;t t
|
||||
EOF
|
||||
_RTEMS_UPDATE_CONDITIONAL([started/tversions.sed],[started/tversions.sed~])
|
||||
])
|
||||
|
||||
AC_CONFIG_FILES([
|
||||
porting/Makefile
|
||||
networking/Makefile
|
||||
@@ -207,7 +163,7 @@ posix_users/Makefile
|
||||
posix1003.1/Makefile
|
||||
filesystem/Makefile
|
||||
ada_user/Makefile
|
||||
started_ada/Makefile
|
||||
started/Makefile
|
||||
relnotes/Makefile
|
||||
new_chapters/Makefile
|
||||
cpu_supplement/Makefile
|
||||
|
||||
@@ -37,5 +37,6 @@ rtems_header.html
|
||||
rtemspie.pdf
|
||||
sh.texi
|
||||
sparc.texi
|
||||
sparc64.texi
|
||||
states.pdf
|
||||
tic4x.texi
|
||||
+11
-17
@@ -1,5 +1,5 @@
|
||||
#
|
||||
# COPYRIGHT (c) 1988-2002.
|
||||
# COPYRIGHT (c) 1988-2010.
|
||||
# On-Line Applications Research Corporation (OAR).
|
||||
# All rights reserved.
|
||||
#
|
||||
@@ -21,42 +21,43 @@ FILES =
|
||||
info_TEXINFOS = started.texi
|
||||
started_TEXINFOS = $(FILES) $(COMMON_FILES) $(GENERATED_FILES)
|
||||
|
||||
intro.texi: intro.t tversions.texi
|
||||
intro.texi: intro.t
|
||||
$(BMENU2) -c -p "Top" \
|
||||
-u "Top" \
|
||||
-n "Requirements" < $< > $@
|
||||
|
||||
require.texi: require.t tversions.texi
|
||||
require.texi: require.t
|
||||
$(BMENU2) -c -p "GCC Mailing Lists" \
|
||||
-u "Top" \
|
||||
-n "Prebuilt Toolset Executables" < $< > $@
|
||||
|
||||
binaries.texi: binaries.t tversions.texi
|
||||
$(BMENU2) -c -p "Archive and Build Directory Format" \
|
||||
binaries.texi: binaries.t
|
||||
$(BMENU2) -c \
|
||||
-p "GNU/Linux Distrobutions using Debian Packaging Format" \
|
||||
-u "Top" \
|
||||
-n "Building the GNU Cross Compiler Toolset" < $< > $@
|
||||
|
||||
buildc.texi: buildc.t tversions.texi
|
||||
buildc.texi: buildc.t
|
||||
$(BMENU2) -c -p "Removing Zipped Tar Files" \
|
||||
-u "Top" \
|
||||
-n "Building RTEMS" < $< > $@
|
||||
|
||||
buildrt.texi: buildrt.t tversions.texi
|
||||
buildrt.texi: buildrt.t
|
||||
$(BMENU2) -c -p "Error Messages Indicating Configuration Problems" \
|
||||
-u "Top" \
|
||||
-n "Building the Sample Applications" < $< > $@
|
||||
|
||||
sample.texi: sample.t tversions.texi
|
||||
sample.texi: sample.t
|
||||
$(BMENU2) -c -p "Using the RTEMS configure Script Directly" \
|
||||
-u "Top" \
|
||||
-n "Where To Go From Here" < $< > $@
|
||||
|
||||
nextstep.texi: nextstep.t tversions.texi
|
||||
nextstep.texi: nextstep.t
|
||||
$(BMENU2) -c -p "More Information on RTEMS Application Makefiles" \
|
||||
-u "Top" \
|
||||
-n "Using MS-Windows as a Development Host" < $< > $@
|
||||
|
||||
nt.texi: nt.t tversions.texi
|
||||
nt.texi: nt.t
|
||||
$(BMENU2) -c -p "Writing an Application" \
|
||||
-u "Top" \
|
||||
-n "" < $< > $@
|
||||
@@ -82,11 +83,4 @@ PICTURES = pictures/bit_ada.jpg pictures/bit_ada.vsd pictures/bit_c.jpg \
|
||||
|
||||
EXTRA_DIST += $(PICTURES)
|
||||
|
||||
tversions.texi: tversions.texi.in tversions.sed
|
||||
sed -f tversions.sed $(srcdir)/tversions.texi.in > tversions.texi
|
||||
CLEANFILES += tversions.texi
|
||||
|
||||
EXTRA_DIST += tversions.texi.in
|
||||
DISTCLEANFILES = tversions.sed
|
||||
|
||||
CLEANFILES += started.info started.info-?
|
||||
+256
-69
File diff suppressed because it is too large.
Load diff
+480
-622
File diff suppressed because it is too large.
Load diff
+66
-68
File diff suppressed because it is too large.
Load diff
+10
-24
@@ -1,5 +1,5 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -18,7 +18,7 @@ essentials for performing a setup of the following items:
|
||||
@itemize @bullet
|
||||
@item GNU Cross Compilation Tools for RTEMS on your build-host system
|
||||
@item RTEMS OS for the target
|
||||
@item GDB Debugger
|
||||
@item GNU Debugger (GDB)
|
||||
@end itemize
|
||||
|
||||
The remainder of this chapter provides background information on real-time
|
||||
@@ -159,31 +159,17 @@ http://www.gnu.org/manual/manual.html}
|
||||
|
||||
@uref{mailto:@value{RTEMSUSERS},@value{RTEMSUSERS}}
|
||||
|
||||
This mailing list is dedicated to the discussion of issues related
|
||||
to RTEMS, including GNAT/RTEMS. If you have questions about RTEMS,
|
||||
wish to make suggestions, or just want to pick up hints, this is a
|
||||
good list to monitor. Subscribe by sending an empty mail message to
|
||||
@uref{mailto:@value{RTEMSUSERSSUBSCRIBE},@value{RTEMSUSERSSUBSCRIBE}}.
|
||||
Messages sent to @uref{mailto:@value{RTEMSUSERS},@value{RTEMSUSERS}}
|
||||
are posted to the list.
|
||||
|
||||
@subsection CrossGCC Mailing List
|
||||
|
||||
@uref{mailto:crossgcc@@sources.redhat.com,crossgcc@@sources.redhat.com}
|
||||
|
||||
This mailing list is dedicated to the use of the GNU tools in
|
||||
cross development environments. Most of the discussions
|
||||
focus on embedded issues. Information on subscribing
|
||||
to this mailing list is included in the
|
||||
@uref{http://www.objsw.com/CrossGCC/,CrossGCC FAQ}.
|
||||
|
||||
The CrossGCC FAQ and Wiki are are available
|
||||
at @uref{http://www.billgatliff.com,http://www.billgatliff.com}.
|
||||
This is the primary mailing list for the discussion of issues
|
||||
related to RTEMS, including GNAT/RTEMS. If you have questions
|
||||
about RTEMS, wish to make suggestions, track development efforts,
|
||||
or just want to pick up hints, this is a good list to monitor.
|
||||
If you would like to browse the thousands of messages in the fifteen
|
||||
year archive of the mailing list or subscribe to it, please visit
|
||||
@uref{http://www.rtems.org/mailman,http://www.rtems.org/mailman} for
|
||||
more information,
|
||||
|
||||
@subsection GCC Mailing Lists
|
||||
|
||||
|
||||
The GCC Project is hosted at @uref{http://gcc.gnu.org,http://gcc.gnu.org}.
|
||||
They maintain multiple mailing lists that are described at the web site
|
||||
along with subscription information.
|
||||
|
||||
+70
-81
@@ -1,6 +1,5 @@
|
||||
@c
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -9,74 +8,70 @@
|
||||
|
||||
@chapter Where To Go From Here
|
||||
|
||||
At this point, you should have successfully installed a
|
||||
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
|
||||
and run it. What do you do next?
|
||||
At this point, you should have successfully installed a 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 and run it. What do you do next?
|
||||
|
||||
The answer is that it depends. You may be interested in
|
||||
writing an application that uses one of the multiple
|
||||
APIs supported by RTEMS. You may need to investigate the
|
||||
network or filesystem support in RTEMS. The common
|
||||
thread is that you are largely finished with this
|
||||
manual and ready to move on to others.
|
||||
The answer is that it depends. You may be interested in writing an
|
||||
application that uses one of the multiple APIs supported by RTEMS.
|
||||
You may need to investigate the network or filesystem support in RTEMS.
|
||||
The common thread is that you are largely finished with this manual and
|
||||
ready to move on to others.
|
||||
|
||||
Whether or not you decide to dive in now and write
|
||||
application code or read some documentation first,
|
||||
this chapter is for you. The first section provides
|
||||
a quick roadmap of some of the RTEMS documentation.
|
||||
The next section provides a brief overview of the
|
||||
RTEMS application structure.
|
||||
Whether or not you decide to dive in now and write application code or
|
||||
read some documentation first, this chapter is for you. The first section
|
||||
provides a quick roadmap of some of the RTEMS documentation. The next
|
||||
section provides a brief overview of the RTEMS application structure.
|
||||
|
||||
@section Documentation Overview
|
||||
|
||||
When writing RTEMS applications, you should find the
|
||||
following manuals useful because they define the
|
||||
calling interface to many of the services provided
|
||||
by RTEMS:
|
||||
When writing RTEMS applications, you should find the following manuals
|
||||
useful because they define the calling interface to many of the services
|
||||
provided by RTEMS:
|
||||
|
||||
@itemize @bullet
|
||||
@item @b{RTEMS Applications C User's Guide} describes the
|
||||
Classic RTEMS API based on the RTEID specification.
|
||||
|
||||
@item @b{RTEMS POSIX API User's Guide} describes the
|
||||
RTEMS POSIX API that is based on the POSIX 1003.1b API.
|
||||
@item @b{RTEMS POSIX API User's Guide} describes the RTEMS POSIX API
|
||||
that is based on the POSIX 1003.1b API. If there is any place where
|
||||
this manual is thin or unclear, please refer to the OpenGroup Single
|
||||
UNIX Specification. RETEMS tracks that specification for future POSIX
|
||||
revisions.
|
||||
|
||||
@item @b{RTEMS Network Supplement} provides information
|
||||
on the network services provided by RTEMS.
|
||||
@item @b{RTEMS Network Supplement} provides information on the network
|
||||
services provided by RTEMS. RTEMS provides a BSD sockets programming
|
||||
interface so any network programming book should be helpful.
|
||||
|
||||
@end itemize
|
||||
|
||||
In addition, the following manuals from the GNU Cross
|
||||
Compilation Toolset include information on run-time services
|
||||
available.
|
||||
In addition, the following manuals from the GNU Cross Compilation Toolset
|
||||
include information on run-time services available.
|
||||
|
||||
@itemize @bullet
|
||||
@item @b{Cygnus C Support Library} describes the Standard
|
||||
C Library functionality provided by Newlib's libc.
|
||||
@item @b{Cygnus C Support Library} describes the Standard C Library
|
||||
functionality provided by Newlib's libc.
|
||||
|
||||
@item @b{Cygnus C Math Library} describes the Standard
|
||||
C Math Library functionality provided by Newlib's libm.
|
||||
@item @b{Cygnus C Math Library} describes the Standard C Math Library
|
||||
functionality provided by Newlib's libm.
|
||||
|
||||
@end itemize
|
||||
|
||||
Finally, the RTEMS FAQ and mailing list archives are available
|
||||
at @uref{@value{RTEMSHTTPURL}}.
|
||||
Finally, the RTEMS FAQ, Wiki, and mailing list archives are available
|
||||
at @uref{http://www.rtems.org, http://www.rtems.org}.
|
||||
|
||||
There is a wealth of documentation available for RTEMS and
|
||||
the GNU tools supporting it. If you run into something
|
||||
that is not clear or missing, bring it to our attention.
|
||||
There is a wealth of documentation available for RTEMS and the GNU tools
|
||||
supporting it. If you run into something that is not clear or missing,
|
||||
bring it to our attention.
|
||||
|
||||
Also, some of the RTEMS documentation is still under
|
||||
construction. If you would like to contribute to this
|
||||
effort, please contact the RTEMS Team at
|
||||
@uref{mailto:@value{RTEMSUSERS}, @value{RTEMSUSERS}}.
|
||||
If you are interested in sponsoring the development of a new
|
||||
feature, BSP, device driver, port of an existing library, etc.,
|
||||
please contact one of the RTEMS Service Providers listed
|
||||
at @uref{@value{RTEMSHTTPURL}/support.html,@value{RTEMSHTTPURL}/support.html}.
|
||||
Also, some of the RTEMS documentation is still under construction.
|
||||
If you would like to contribute to this effort, please contact the
|
||||
RTEMS Team at @uref{mailto:@value{RTEMSUSERS}, @value{RTEMSUSERS}}.
|
||||
If you are interested in sponsoring the development of a new feature,
|
||||
BSP, device driver, port of an existing library, etc., please contact
|
||||
@uref{mailto:sales@@oarcorp.com, sales@@oarcorp.com}.
|
||||
|
||||
@section Writing an Application
|
||||
|
||||
@@ -86,29 +81,25 @@ RTEMS provides a single process, multi-threaded run-time
|
||||
environment. However there are two important things that are
|
||||
different from a standard UNIX hosted program.
|
||||
|
||||
First, the application developer must provide configuration
|
||||
information for RTEMS. This configuration information
|
||||
includes limits on the maximum number of various OS resources
|
||||
available and networking configuration among other things.
|
||||
See the @b{Configuring a System} in the
|
||||
@b{RTEMS Applications C User's Guide} for more details.
|
||||
First, the application developer must provide configuration information
|
||||
for RTEMS. This configuration information includes limits on the maximum
|
||||
number of various OS resources available and networking configuration
|
||||
among other things. See the @b{Configuring a System} in the @b{RTEMS
|
||||
Applications C User's Guide} for more details.
|
||||
|
||||
Second, RTEMS applications may or may not start at
|
||||
@code{main()}. Applications begin execution at
|
||||
one or more user configurable application
|
||||
initialization tasks or threads. It is possible
|
||||
to configure an application to start with a
|
||||
single thread that whose entry point is @code{main()}.
|
||||
Second, RTEMS applications may or may not start at @code{main()}.
|
||||
Applications begin execution at one or more user configurable application
|
||||
initialization tasks or threads. It is possible to configure an
|
||||
application to start with a single thread that whose entry point is
|
||||
@code{main()}.
|
||||
|
||||
Each API supported by RTEMS (Internal, Classic, and POSIX)
|
||||
allows the user to configure a set of one or more tasks
|
||||
that are created and started automatically
|
||||
during RTEMS initialization. The RTEMS Automatic
|
||||
Configuration Generation (@code{confdefs.h}) scheme can be
|
||||
used to easily generate the configuration information for
|
||||
an application that starts with a single initialization task.
|
||||
By convention, unless overridden, the default name of the
|
||||
initialization task varies based up API.
|
||||
Each API supported by RTEMS (Internal, Classic, and POSIX) allows
|
||||
the user to configure a set of one or more tasks that are created and
|
||||
started automatically during RTEMS initialization. The RTEMS Automatic
|
||||
Configuration Generation (@code{confdefs.h}) scheme can be used to easily
|
||||
generate the configuration information for an application that starts
|
||||
with a single initialization task. By convention, unless overridden,
|
||||
the default name of the initialization task varies based up API.
|
||||
|
||||
@itemize @bullet
|
||||
@item @code{Init} - single Classic API Initialization Task
|
||||
@@ -129,17 +120,15 @@ file @code{init.c} usually contains the initialization task. Although
|
||||
not required, in most of the examples, the initialization task
|
||||
completes by deleting itself.
|
||||
|
||||
As you begin to write RTEMS application code, you may be confused
|
||||
by the range of alternatives. Supporting multiple tasking
|
||||
APIs can make the choices confusing. Many application groups
|
||||
writing new code choose one of the APIs as their primary API
|
||||
and only use services from the others if nothing comparable
|
||||
is in their preferred one. However, the support for multiple
|
||||
APIs is a powerful feature when integrating code from multiple
|
||||
sources. You can write new code using POSIX services and
|
||||
still use services written in terms of the other APIs.
|
||||
Moreover, by adding support for yet another API, one could
|
||||
provide the infrastructure required to migrate from a
|
||||
legacy RTOS with a non-standard API to an API like POSIX.
|
||||
As you begin to write RTEMS application code, you may be confused by the
|
||||
range of alternatives. Supporting multiple tasking APIs can make the
|
||||
choices confusing. Many application groups writing new code choose one
|
||||
of the APIs as their primary API and only use services from the others if
|
||||
nothing comparable is in their preferred one. However, the support for
|
||||
multiple APIs is a powerful feature when integrating code from multiple
|
||||
sources. You can write new code using POSIX services and still use
|
||||
services written in terms of the other APIs. Moreover, by adding support
|
||||
for yet another API, one could provide the infrastructure required to
|
||||
migrate from a legacy RTOS with a non-standard API to an API like POSIX.
|
||||
|
||||
|
||||
+43
-60
@@ -1,5 +1,5 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -15,31 +15,24 @@ This chapter was originally written by
|
||||
@uref{mailto:g_montel@@yahoo.com, Geoffroy Montel <g_montel@@yahoo.com>}
|
||||
with input from
|
||||
@uref{mailto:<D.J@@fiddes.surfaid.org>, David Fiddes <D.J@@fiddes.surfaid.org>}.
|
||||
It was based upon his successful but unnecessarily
|
||||
painful efforts with Cygwin beta versions.
|
||||
Cygwin and this chapter have been updated multiple times since
|
||||
those early days although their pioneering efforts
|
||||
and input is still greatly appreciated.
|
||||
It was based upon his successful but unnecessarily painful efforts with
|
||||
Cygwin beta versions. Cygwin and this chapter have been updated multiple
|
||||
times since those early days although their pioneering efforts and input
|
||||
is still greatly appreciated.
|
||||
|
||||
@section Microsoft Windows Version Requirements
|
||||
|
||||
RTEMS users report fewer problems when using Microsoft
|
||||
Windows NT, 2000, or XP. Although, the open source tools
|
||||
that are used in RTEMS development do execute on Windows 95,
|
||||
98, or ME, they tend to be more stable when used with
|
||||
the modern Windows variants.
|
||||
RTEMS users report fewer problems when using Microsoft Windows XP or newer.
|
||||
|
||||
@section Cygwin
|
||||
|
||||
For RTEMS development, the recommended approach is to use
|
||||
Cygwin 1.0 or later. Cygwin is available from
|
||||
@uref{http://sources.redhat.com/cygwin, http://sources.redhat.com/cygwin}
|
||||
Recent versions of Cygwin are vastly improved over the beta
|
||||
versions. Most of the oddities, instabilities, and performance
|
||||
problems have been resolved. The installation procedure
|
||||
is much simpler. However, there are a handful of issues
|
||||
that remain to successfully use Cygwin as an RTEMS development
|
||||
environment.
|
||||
For RTEMS development, the recommended approach is to use Cygwin. Cygwin
|
||||
is available from @uref{http://www.cygwin.com, http://www.cygwin.com} .
|
||||
The primary issues reported by users of Cygwin is that it is slower
|
||||
on the same hardware than a native GNU/Linux installation and strange
|
||||
issues over carriage return/line feed inconsistencies between UNIX and
|
||||
Windows environments. However, there are a handful of other issues that
|
||||
may turn up when using Cygwin as an RTEMS development environment.
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@@ -79,18 +72,17 @@ shell scripts properly.
|
||||
filesystem (e.g. mounted with the @code{-b} option). Otherwise,
|
||||
many confusing errors will result.
|
||||
|
||||
@item A user has reported that they needed
|
||||
to set CYGWIN=ntsec for chmod to work correctly, but had to set
|
||||
CYGWIN=nontsec for compile to work properly (otherwise there were
|
||||
complaints about permissions on a temporary file).
|
||||
@item A user has reported that they needed to set @code{CYGWIN=ntsec}
|
||||
for chmod to work correctly, but had to set @code{CYGWIN=nontsec}
|
||||
for compile to work properly (otherwise there were complaints about
|
||||
permissions on a temporary file).
|
||||
|
||||
@item If you want to build the tools from source, you have the
|
||||
same options as UNIX users.
|
||||
|
||||
@item You may have to uncompress archives during this
|
||||
process. You must @b{NOT} use @code{WinZip} or
|
||||
@code{PKZip}. Instead the un-archiving process uses
|
||||
the GNU @code{zip} and @code{tar} programs as shown below:
|
||||
@item You may have to uncompress archives during this process. You must
|
||||
@b{NOT} use @code{WinZip} or @code{PKZip}. Instead the un-archiving
|
||||
process uses the GNU @code{zip} and @code{tar} programs as shown below:
|
||||
|
||||
@example
|
||||
tar -xzvf archive.tgz
|
||||
@@ -102,20 +94,18 @@ tar -xzvf archive.tgz
|
||||
|
||||
@section Text Editor
|
||||
|
||||
You absolutely have to use a text editor which can
|
||||
save files with Unix format. So do @b{NOT} use Notepad
|
||||
or Wordpad! There are a number of editors
|
||||
freely available that can be used.
|
||||
You absolutely have to use a text editor which can save files with Unix
|
||||
format. So do @b{NOT} use Notepad or Wordpad! There are a number of
|
||||
editors freely available that can be used.
|
||||
|
||||
@itemize @bullet
|
||||
@item @b{VIM} (@b{Vi IMproved}) is available from
|
||||
@uref{http://www.vim.org/,http://www.vim.org/}.
|
||||
This editor has the very handy ability to easily
|
||||
read and write files in either DOS or UNIX style.
|
||||
@uref{http://www.vim.org/,http://www.vim.org/}. This editor has the very
|
||||
handy ability to easily read and write files in either DOS or UNIX style.
|
||||
|
||||
@item @b{GNU Emacs} is available for many platforms
|
||||
including MS-Windows. The official homepage
|
||||
is @uref{http://www.gnu.org/software/emacs/emacs.html,
|
||||
including MS-Windows. The official homepage is
|
||||
@uref{http://www.gnu.org/software/emacs/emacs.html,
|
||||
http://www.gnu.org/software/emacs/emacs.html}.
|
||||
The GNU Emacs on Windows NT and Windows 95/98 FAQ is at
|
||||
@uref{http://www.gnu.org/software/emacs/windows/ntemacs.html,
|
||||
@@ -123,11 +113,10 @@ http://www.gnu.org/software/emacs/windows/ntemacs.html}.
|
||||
|
||||
@end itemize
|
||||
|
||||
If you do accidentally end up with files
|
||||
having MS-DOS style line termination, then you
|
||||
may have to convert them to Unix format for some
|
||||
Cygwin programs to operate on them properly. The
|
||||
program @code{dos2unix} can be used to put them
|
||||
If you do accidentally end up with files having MS-DOS style line
|
||||
termination, then you may have to convert them to Unix format for some
|
||||
Cygwin programs to operate on them properly. The program @code{dos2unix}
|
||||
can be used to put them
|
||||
back into Unix format as shown below:
|
||||
|
||||
@example
|
||||
@@ -137,22 +126,16 @@ Dos2Unix: Cleaning file XYZ ...
|
||||
|
||||
@section System Requirements
|
||||
|
||||
Although the finished cross-compiler is fairly easy on resources,
|
||||
building it can take a significant amount of processing power and
|
||||
disk space.
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@item The faster the CPU, the better. The tools and Cygwin can be
|
||||
@b{very} CPU hungry.
|
||||
|
||||
@item The more RAM, the better. Reports are that when building GCC
|
||||
and GDB, peak memory usage can exceed 256 megabytes.
|
||||
|
||||
@item The more disk space, the better. You need more if you are building
|
||||
the GNU tools and the amount of disk space for binaries is obviously
|
||||
directly dependent upon the number of CPUs you have cross toolsets
|
||||
installed for.
|
||||
|
||||
@end itemize
|
||||
Although the finished cross-compiler is fairly easy on resources, building
|
||||
it can take a significant amount of processing power and disk space.
|
||||
Luckily, desktop computers have progressed very far since this guide
|
||||
was originally written so it is unlikely you will have any problems.
|
||||
Just do not use an old cast-off machine with < 1 GB RAM and a 1 Ghz CPU.
|
||||
Unless, of course, you enjoy waiting for things to complete.
|
||||
|
||||
The more disk space, the better. You need more if you are building the
|
||||
GNU tools and the amount of disk space for binaries is obviously directly
|
||||
dependent upon the number of CPUs you have cross toolsets installed for.
|
||||
In addition to the disk space requirements documented earlier for tool
|
||||
building, you will also have to have enough space to install the Cygwin
|
||||
environment.
|
||||
+29
-84
@@ -1,5 +1,5 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -21,19 +21,18 @@ assessing the amount of disk space required for your installation:
|
||||
+------------------------------------+--------------------------+
|
||||
| Component | Disk Space Required |
|
||||
+------------------------------------+--------------------------+
|
||||
| archive directory | 55 Mbytes |
|
||||
| tools src unarchived | 350 Mbytes |
|
||||
| each individual build directory | up to 750 Mbytes |
|
||||
| each installation directory | 20-200 Mbytes |
|
||||
| archive directory | 120 Mbytes |
|
||||
| tools src unarchived | 1400 Mbytes |
|
||||
| each individual build directory | up to 2500 Mbytes |
|
||||
| each installation directory | 900 Mbytes |
|
||||
+------------------------------------+--------------------------+
|
||||
@end example
|
||||
|
||||
It is important to understand that the above requirements only address
|
||||
the GNU C/C++ Cross Compiler Tools themselves. Adding additional
|
||||
languages such as Fortran or Objective-C can increase the size
|
||||
of the build and installation directories. Also, the unarchived
|
||||
source and build directories can be removed after the tools are
|
||||
installed.
|
||||
It is important to understand that the above requirements only address the
|
||||
GNU C/C++ Cross Compiler Tools themselves. Adding additional languages
|
||||
such as Ada or Go can increase the size of the build and installation
|
||||
directories. Also, the unarchived source and build directories can be
|
||||
removed after the tools are installed.
|
||||
|
||||
After the tools themselves are installed, RTEMS must be built
|
||||
and installed for each Board Support Package that you wish
|
||||
@@ -46,8 +45,11 @@ will tend to be in the 40-60 Mbyte range.
|
||||
There are a number of factors which must be taken into
|
||||
account in order to estimate the amount of disk space required
|
||||
to build RTEMS itself. Attempting to build multiple BSPs in
|
||||
a single step increases the disk space requirements. Similarly
|
||||
enabling optional features increases the build and install
|
||||
a single step increases the disk space requirements. One some
|
||||
target architectures, this can lead to disk usage during the build
|
||||
of over one gigabyte.
|
||||
|
||||
Similarly enabling optional features increases the build and install
|
||||
space requirements. In particular, enabling and building
|
||||
the RTEMS tests results in a significant increase in build
|
||||
space requirements but since the tests are not installed has,
|
||||
@@ -56,8 +58,9 @@ enabling them has no impact on installation requirements.
|
||||
@section General Host Software Requirements
|
||||
|
||||
The instructions in this manual should work on any computer running
|
||||
a UNIX variant. Some native GNU tools are used by this procedure
|
||||
including:
|
||||
a POSIX environment including GNU/Linux and Cygwin. Mingw users may
|
||||
encounter additional issues due to the limited POSIX compatibility.
|
||||
Some native GNU tools are used by this procedure including:
|
||||
|
||||
@itemize @bullet
|
||||
@item GCC
|
||||
@@ -65,8 +68,10 @@ including:
|
||||
@item GNU makeinfo
|
||||
@end itemize
|
||||
|
||||
In addition, some native utilities may be deficient for building
|
||||
the GNU tools.
|
||||
In addition, some native utilities may be deficient for building the
|
||||
GNU tools. On hosts which have m4 but it is not GNU m4, it is not
|
||||
uncommon to have to install GNU m4. Similarly, some shells are not
|
||||
capable of fully supporting the RTEMS configure scripts.
|
||||
|
||||
@subsection GCC
|
||||
|
||||
@@ -129,9 +134,10 @@ are on a Solaris 2.x host, then use the @code{/bin/ksh} or
|
||||
|
||||
@end itemize
|
||||
|
||||
@subsection Linux
|
||||
@subsection Distribution Independent Potential GNU/Linux Issues
|
||||
|
||||
The following problems have been reported by Linux users:
|
||||
The following problems have been reported by users of various GNU/Linux
|
||||
distributions:
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@@ -149,71 +155,10 @@ to at least GNU fileutils version 3.16 to resolve this problem.
|
||||
|
||||
@end itemize
|
||||
|
||||
@section Archive and Build Directories
|
||||
@subsection GNU/Linux Distrobutions using Debian Packaging Format
|
||||
|
||||
If you are using RPM or another packaging format that supports
|
||||
building a package from source, then there is probably a directory
|
||||
structure assumed by that packaging format. Otherwise, you
|
||||
are free to use whatever organization you like. However, this
|
||||
document will use the directory organization described
|
||||
in @ref{Archive and Build Directory Format}.
|
||||
|
||||
@subsection RPM Archive and Build Directory Format
|
||||
|
||||
For RPM, it is assumed that the following subdirectories
|
||||
are under a root directory such as @code{/usr/src/redhat}:
|
||||
|
||||
@example
|
||||
BUILD
|
||||
RPMS
|
||||
SOURCES
|
||||
SPECS
|
||||
SRPMS
|
||||
@end example
|
||||
|
||||
For the purposes of this document, the RPM @code{SOURCES} directory
|
||||
is the directory into which all tool source and patches are
|
||||
assumed to reside. The @code{BUILD} directory is where the actual
|
||||
build is performed when building binaries from a source RPM.
|
||||
The @code{SOURCES} and @code{BUILD} are logically equivalent to
|
||||
the @code{archive} and @code{tools} directory discussed in the
|
||||
next section.
|
||||
|
||||
@subsection Archive and Build Directory Format
|
||||
|
||||
When no packaging format requirements are present, the root directory for
|
||||
the storage of source archives and patches as well as for building the
|
||||
tools is up to the user. The only concern is that there be enough
|
||||
disk space to complete the build. In this document, the following
|
||||
organization will be used.
|
||||
|
||||
Make an @code{archive} directory to contain the downloaded
|
||||
source code and a @code{tools} directory to be used as a build
|
||||
directory. The command sequence to do this is shown
|
||||
below:
|
||||
|
||||
@example
|
||||
mkdir archive
|
||||
mkdir tools
|
||||
@end example
|
||||
|
||||
This will result in an initial directory structure similar to the
|
||||
one shown in the following figure:
|
||||
|
||||
@example
|
||||
@group
|
||||
/whatever/prefix/you/choose/
|
||||
archive/
|
||||
tools/
|
||||
|
||||
@end group
|
||||
@end example
|
||||
|
||||
@c @ifset use-html
|
||||
@c @html
|
||||
@c <IMG SRC="sfile12c.jpg" WIDTH=417 HEIGHT=178
|
||||
@c ALT="Starting Directory Organization">
|
||||
@c @end html
|
||||
@c @end ifset
|
||||
The RTEMS Project does not currently provide prebuilt toolsets in the Debian packaging format used by the Debian and Ubuntu distributions. If you are using a distribution using this packaging format, then you have two options for installing the RTEMS toolset.
|
||||
|
||||
The first option is to build the toolset from source following the instructions in the @ref{Building the GNU Cross Compiler Toolset}. This is an approach taken by many users.
|
||||
|
||||
Alternatively, it is often possible to extract the contents of the RPM files which contain the portions of the toolset you require. In this case, you will follow the instructions in @ref{Locating the RPMs for your GNU/Linux Distribution} but assume your distribution is the RedHat Enterprise Linux version which is closest to yours from a shared library perspective. As of December 2010, this is usually RedHat Enterprise Linux version 5. As time passes, it is expected that version 6 will be appropriate in more cases. You will extract the contents of these RPM files using either @code{rpm2cpio} and install them or you may be able to use the @code{alien} tool to convert them to Debian packaging.
|
||||
+27
-55
@@ -1,5 +1,5 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -52,7 +52,7 @@ to your target board and executed is very dependent
|
||||
on the board you are using. The following is a list of
|
||||
commonly used BSPs classified by their RTEMS CPU family and pointers
|
||||
to instructions on how to use them. [NOTE: All file names should be
|
||||
prepended with @value{RTEMSUNTAR}/c/src/lib/libbsp.]
|
||||
prepended with @code{rtems-@value{RTEMSAPI}.<VERSION>/c/src/lib/libbsp}.]
|
||||
|
||||
@need 1000
|
||||
@table @b
|
||||
@@ -147,31 +147,11 @@ the following to unarchive the sample applications:
|
||||
|
||||
@example
|
||||
cd tools
|
||||
tar xjf ../archive/examples-VERSION.tgz
|
||||
tar xjf ../archive/examples-v2-@value{RTEMSAPI}.<VERSION>.tgz
|
||||
@end example
|
||||
|
||||
The sample applications most likely to be of interest to you are:
|
||||
|
||||
@itemize @bullet
|
||||
@item hello_world_c - C Hello World application with a simple
|
||||
RTEMS configuration and an entry point not called @code{main()}.
|
||||
|
||||
@item simple_main - Very simple program starting at @code{main()}
|
||||
and shutting down RTEMS via @code{exit()} without any other operations.
|
||||
It uses the default configuration inside RTEMS which is only
|
||||
intended to satisfy @code{autoconf} probes and extremely simple
|
||||
console-based applications.
|
||||
|
||||
@item libcpp - Simple C++ library for RTEMS showing how to build an
|
||||
application library written in C++.
|
||||
|
||||
@item psx_sched_report - POSIX Scheduler Reporter is a program
|
||||
that prints out some scheduler attributes of the RTEMS POSIX API.
|
||||
|
||||
@end itemize
|
||||
|
||||
Each tests is found in a separate subdirectory and built using the
|
||||
same command sequence. The @code{hello_world_c} sample will be used
|
||||
Each tests is found in a separate subdirectory and built using the same
|
||||
command sequence. The @code{hello/hello_world_c} sample will be used
|
||||
as an example.
|
||||
|
||||
@c
|
||||
@@ -192,25 +172,24 @@ If the sample application has successfully been built, then the application
|
||||
executable is placed in the following directory:
|
||||
|
||||
@example
|
||||
hello_world_c/o-optimize/<filename>.exe
|
||||
hello_world_c/o-optimize/<filename>.ralf
|
||||
@end example
|
||||
|
||||
The other C/C++ sample applications are built using a similar procedure.
|
||||
The other sample applications are built using a similar procedure.
|
||||
|
||||
@c
|
||||
@c Ada Sample Applications
|
||||
@c
|
||||
@section Ada Sample Applications
|
||||
|
||||
The Ada sample application set primarily includes a
|
||||
a simple Hello World Ada program which can be used
|
||||
as a starting point for GNAT/RTEMS applications.
|
||||
Use the following command to unarchive the Ada sample
|
||||
The Ada sample application set primarily includes a a simple Hello
|
||||
World Ada program which can be used as a starting point for GNAT/RTEMS
|
||||
applications. Use the following command to unarchive the Ada sample
|
||||
applications:
|
||||
|
||||
@example
|
||||
cd tools
|
||||
tar xjf ../archive/ada-examples-@value{VERSION}.tar.bz2
|
||||
tar xjf ../archive/ada-examples-@value{RTEMSAPI}.<VERSION>.tgz
|
||||
@end example
|
||||
|
||||
@subheading Create a BSP Specific Makefile
|
||||
@@ -219,11 +198,7 @@ Currently, the procedure for building and linking an Ada application
|
||||
is a bit more difficult than a C or C++ application. This is certainly
|
||||
an opportunity for a volunteer project.
|
||||
|
||||
At this time, there is a
|
||||
|
||||
Provided are example Makefiles for multiple BSPs. Copy one of these to
|
||||
the file Makefile.<BOARD_SUPPORT_PACKAGE> and edit it as appropriate for
|
||||
your local configuration.
|
||||
If your BSP requires special arguments when linking, you may have to augment the file @code{ada-examples-@value{RTEMSAPI}.<VERSION>/Makefile.shared}. Most RTEMS BSPs do not require special linking arguments so this should not be frequently needed.
|
||||
|
||||
Use the <INSTALLATION_POINT> and <BOARD_SUPPORT_PACKAGE> specified when
|
||||
configuring and installing RTEMS.
|
||||
@@ -233,18 +208,13 @@ configuring and installing RTEMS.
|
||||
Use the following command to start the build of the sample application:
|
||||
|
||||
@example
|
||||
cd tools/hello_world_ada
|
||||
make -f Makefile.<BOARD_SUPPORT_PACKAGE>
|
||||
cd tools/ada-examples-@value{RTEMSAPI}.<VERSION>/ada-examples/hello_world_ada
|
||||
@end example
|
||||
|
||||
NOTE: GNU make is the preferred @code{make} utility. Other @code{make}
|
||||
implementations may work but all testing is done with GNU make.
|
||||
|
||||
If the BSP specific modifications to the Makefile were correct and
|
||||
no errors are detected during the sample application build, it is
|
||||
If no errors are detected during the sample application build, it is
|
||||
reasonable to assume that the build of the GNAT/RTEMS Cross Compiler Tools
|
||||
for RTEMS and RTEMS itself for the selected host and target
|
||||
combination was done properly.
|
||||
for RTEMS and RTEMS itself for the selected host and target combination
|
||||
was done properly.
|
||||
|
||||
@section Application Executable
|
||||
|
||||
@@ -252,7 +222,7 @@ If the sample application has successfully been build, then the application
|
||||
executable is placed in the following directory:
|
||||
|
||||
@example
|
||||
tools/hello_world_ada/o-optimize/<filename>.exe
|
||||
tools/@code{ada-examples-@value{RTEMSAPI}.<VERSION>}/hello_world_ada/o-optimize/<filename>.exe
|
||||
@end example
|
||||
|
||||
How this executable is downloaded to the target board is very dependent
|
||||
@@ -263,12 +233,14 @@ on the BOARD_SUPPORT_PACKAGE selected.
|
||||
@c
|
||||
@section More Information on RTEMS Application Makefiles
|
||||
|
||||
These sample applications are examples of simple
|
||||
RTEMS applications that use the RTEMS Application Makefile
|
||||
system. This Makefile system simplifies building
|
||||
RTEMS applications by providing Makefile templates and
|
||||
capturing the configuration information used to build
|
||||
RTEMS specific to your BSP. Building an RTEMS application
|
||||
for different BSPs is as simple as switching the
|
||||
setting of @code{RTEMS_MAKEFILE_PATH}. This Makefile
|
||||
These sample applications are examples of simple RTEMS applications
|
||||
that use the RTEMS Application Makefile system. This Makefile system
|
||||
simplifies building RTEMS applications by providing Makefile templates and
|
||||
capturing the configuration information used to build RTEMS specific to
|
||||
your BSP. Building an RTEMS application for different BSPs is as simple
|
||||
as switching the setting of @code{RTEMS_MAKEFILE_PATH}. This Makefile
|
||||
system is described in the file @code{make/README}.
|
||||
|
||||
It is very likely in the future that the RTEMS examples built using an
|
||||
installed RTEMS will be converted to autoconf.
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
@c %**end of header
|
||||
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c COPYRIGHT (c) 1988-2010.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@@ -23,11 +23,6 @@
|
||||
@include common/setup.texi
|
||||
@include common/rtems.texi
|
||||
|
||||
@c
|
||||
@c Now set all the tool version dependent information
|
||||
@c
|
||||
@include tversions.texi
|
||||
|
||||
@ifset use-ascii
|
||||
@dircategory RTEMS On-Line Manual
|
||||
@direntry
|
||||
|
||||
@@ -1,91 +0,0 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-2002.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@c $Id$
|
||||
@c
|
||||
|
||||
@c
|
||||
@c This file contains all toolset version dependent information
|
||||
@c
|
||||
|
||||
@c
|
||||
@c Comment out setting the "XYZ-RTEMSPATCH" variable if there is no
|
||||
@c patch required. The documentation will detect this and print
|
||||
@c an appropriate message in a short section.
|
||||
@c
|
||||
|
||||
|
||||
@c
|
||||
@c GCC Version
|
||||
@c
|
||||
|
||||
@set GCCVERSION @GCCVERSION@
|
||||
@set GCCUNTAR gcc-@value{GCCVERSION}
|
||||
@set GCCTAR @value{GCCUNTAR}.tar.bz2
|
||||
@set GCCFTPSITE ftp.gnu.org
|
||||
@set GCCFTPDIR /pub/gnu/gcc/@value{GCCUNTAR}
|
||||
@set GCCHTTPDIR /pub/gcc/releases/index.html
|
||||
@SETGCCPATCHVERSION@
|
||||
@ifset GCCPATCHVERSION
|
||||
@set GCCRTEMSPATCH @value{GCCUNTAR}-@value{GCCPATCHVERSION}.diff
|
||||
@end ifset
|
||||
@set GCCRPMRELEASE @GCCRPMRELEASE@
|
||||
|
||||
@c
|
||||
@c BINUTILS Version
|
||||
@c
|
||||
|
||||
@c The "official" binutils
|
||||
@set BINUTILSVERSION @BINUTILSVERSION@
|
||||
@set BINUTILSUNTAR binutils-@value{BINUTILSVERSION}
|
||||
@set BINUTILSTAR @value{BINUTILSUNTAR}.tar.gz
|
||||
@set BINUTILSFTPSITE ftp.gnu.org
|
||||
@set BINUTILSFTPDIR /pub/gnu/binutils
|
||||
@SETBINUTILSPATCHVERSION@
|
||||
@ifset BINUTILSPATCHVERSION
|
||||
@set BINUTILSRTEMSPATCH @value{BINUTILSUNTAR}-@value{BINUTILSPATCHVERSION}.diff
|
||||
@end ifset
|
||||
@set BINUTILSRPMRELEASE @BINUTILSRPMRELEASE@
|
||||
|
||||
@c
|
||||
@c NEWLIB Version
|
||||
@c
|
||||
|
||||
|
||||
@set NEWLIBVERSION @NEWLIBVERSION@
|
||||
@set NEWLIBUNTAR newlib-@value{NEWLIBVERSION}
|
||||
@set NEWLIBTAR @value{NEWLIBUNTAR}.tar.gz
|
||||
@set NEWLIBFTPSITE sources.redhat.com
|
||||
@set NEWLIBFTPDIR /pub/newlib
|
||||
@SETNEWLIBPATCHVERSION@
|
||||
@ifset NEWLIBPATCHVERSION
|
||||
@set NEWLIBRTEMSPATCH @value{NEWLIBUNTAR}-@value{NEWLIBPATCHVERSION}.diff
|
||||
@end ifset
|
||||
|
||||
@c
|
||||
@c GDB Version
|
||||
@c
|
||||
|
||||
@set GDBVERSION @GDBVERSION@
|
||||
@set GDBUNTAR gdb-@value{GDBVERSION}
|
||||
@set GDBTAR @value{GDBUNTAR}.tar.gz
|
||||
@set GDBFTPSITE ftp.gnu.org
|
||||
@set GDBFTPDIR /pub/gnu/gdb
|
||||
@SETGDBPATCHVERSION@
|
||||
@ifset GDBPATCHVERSION
|
||||
@set GDBRTEMSPATCH @value{GDBUNTAR}-@value{GDBPATCHVERSION}.diff
|
||||
@end ifset
|
||||
@set GDBRPMRELEASE @GDBRPMRELEASE@
|
||||
@set GDBFTPURL ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}/@value{GDBTAR}
|
||||
|
||||
@c
|
||||
@c RTEMS Version
|
||||
@c
|
||||
|
||||
@set RTEMSVERSION RTEMS @value{VERSION}
|
||||
@set RTEMSUNTAR rtems-@value{VERSION}
|
||||
@set RTEMSTAR @value{RTEMSUNTAR}.tar.bz2
|
||||
@set RTEMSFTPSITE ftp.rtems.com
|
||||
@set RTEMSFTPDIR /pub/rtems
|
||||
@@ -1,4 +1,4 @@
|
||||
@set UPDATED 27 June 2007
|
||||
@set UPDATED-MONTH June 2007
|
||||
@set UPDATED 14 December 2010
|
||||
@set UPDATED-MONTH December 2010
|
||||
@set EDITION 4.10.99.0
|
||||
@set VERSION 4.10.99.0
|
||||
Reference in new issue
Block a user