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

2010-09-27 Ralf Corsépius <ralf.corsepius@rtems.org>

Browse Source 
* README.configure: Cleanup.
This commit is contained in:
Ralf Corsepius
2010-09-27 04:14:39 +00:00
parent a9fb4f5d2f
commit 91134d863f
2 changed files with 7 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@@ -1,3 +1,7 @@
2010-09-27 Ralf Corsépius <ralf.corsepius@rtems.org>
* README.configure: Cleanup.
2010-06-23 Ralf Corsépius <ralf.corsepius@rtems.org>
* configure.ac: autoconf >= 2.65, automake >= 1.11.

43
README.configure
View File

@@ -11,24 +11,20 @@ tools in the Cygnus one-tree structure. Using autoconf also means
that RTEMS now can be built in a separate build directory.
To re-generate auto*tool generated files (configure, Makefile.in etc),
autoconf-2.59 and automake-1.8 are required.
autoconf-2.68 and automake-1.11.1 are required.
2. Installation
===============
2.1 Standalone build
To configure RTEMS for a specific target, run configure in the build
directory. In addition to the standard configure options, the following
RTEMS-specific option are supported:
--disable-rtems-inlines
--disable-posix
--disable-itron
--enable-itron
--disable-networking
--enable-cxx
--enable-bare-cpu-model=<MODEL>
--enable-bare-cpu-cflags=<FLAGS>
--enable-multiprocessing
--enable-rtemsbsp="bsp1 bsp2 ..."
--enable-tests
@@ -88,8 +84,6 @@ within a target architecture. Remember that the target specifies the
CPU family while the BSP specifies the precise board you will be using.
The following targets are supported:
(none) will build the host-based version on Linux, Solaris and HPUX.
arm-rtems4.10
avr-rtems4.10
bfin-rtems4.10
@@ -104,7 +98,6 @@ The following targets are supported:
powerpc-rtems4.10
sh-rtems4.10
sparc-rtems4.10
bare see notes
The cross-compiler is set to $(target)-gcc by default.
@@ -116,7 +109,7 @@ Installation is done under $(prefix)/rtems.
As an example, to build and install the mvme136 and mvme162 bsps for m68k do:
(path_to_rtems_src)/configure --target=m68k-rtems
(path_to_rtems_src)/configure --target=m68k-rtems4.10
make RTEMS_BSP="mvme136 mvme162"
@@ -128,19 +121,6 @@ test suite.
Documentation is built separately from the source code.
2.2 Target Dependent Notes
bare:
1. See the README in the bare bsp source directory. This should
contain all info you need.
2. The bare bsp source contains a script to show how to build it.
3. The configure flags must be used to get the bare bsp to work.
The --enable-bare-cpu-model and --enable-bare-cpu-cflags are the
only pieces of information. The module is usually a gcc module
such as m68302 or mcpu32. The flags are passed directly to gcc.
Use "" if more than one option is specified.
3. To use the installed RTEMS library
=====================================
@@ -162,8 +142,6 @@ following:
The following bsps are supported:
host-based : posix (on Linux, FreeBSD, Cygwin, Solaris, and HPUX)
arm : csb336 csb337 edb7312 gba gp32 nds rtl22x rtl22xx_t
smdk2410
@@ -171,8 +149,6 @@ avr: : avrtest
bfin : eZKit533 bf537Stamp
c4x : c3xsim c4xsim
h8300 : h8sim
i386 : i386ex pc386 pc386dx pc486 pc586 pc686 pck6 ts_386ex
@@ -215,12 +191,6 @@ sh : gensh1 gensh2 gensh4 simsh1 simsh2 simsh4
sparc : erc32 sis leon2 leon3
any : bare
The following ports were considered obsoleted after the 4.6 releases
and were removed: a29k, hppa, i960, mips64orion, and or32.
5. Makefile structure
=====================
@@ -248,13 +218,6 @@ Please refer to the BSP and Device Driver Guide.
All gnu-based bsps have been built on Linux.
The native (posix) ports have been built and run only on Linux.
The following configurations have NOT been tested:
+ Anything on Nextstep, HPUX and Irix.
+ The C4x and OR32 ports (requires specially patched toolchain)
8. Prerequisites
================