source: rtems/README.configure @ dd2906e

4.104.114.84.95
Last change on this file since dd2906e was 0aa09608, checked in by Joel Sherrill <joel.sherrill@…>, on Nov 8, 2001 at 11:32:21 PM

2001-11-08 Dennis Ehlin (ECS) <Dennis.Ehlin@…>

This modification is part of the submitted modifications necessary to
support the IBM PPC405 family. This submission was reviewed by
Thomas Doerfler <Thomas.Doerfler@…> who ensured it did
not negatively impact the ppc403 BSPs. The submission and tracking
process was captured as PR50.

  • README.configure: Added gen405 BSP.
  • Property mode set to 100644
File size: 9.0 KB
Line 
1#
2#  $Id$
3#
4
51. Autoconf support
6===================
7
8This version of RTEMS is configured with GNU autoconf. RTEMS can be
9configured and built either standalone or together with the compiler
10tools in the Cygnus one-tree structure. Using autoconf also means
11that RTEMS now can be built in a separate build directory.
12
132. Installation
14===============
15
162.1 Standalone build
17
18To configure RTEMS for a specific target, run configure in the build
19directory. In addition to the standard configure options, the following
20RTEMS-specific option are supported:
21
22        --disable-rtems-inlines
23        --disable-posix
24        --disable-itron
25        --disable-networking
26        --enable-cxx
27        --enable-bare-cpu-model=<MODEL>
28        --enable-bare-cpu-cflags=<FLAGS>
29        --enable-gcc28               (also use enable-libcdir when disabled)
30        --enable-libcdir=<DIRECTORY>      (do not use if gcc 2.8 is enabled)
31        --enable-multiprocessing
32        --enable-rtemsbsp="bsp1 bsp2 ..."
33        --enable-tests
34        --enable-rdbg            (only valid for i386 and some PowerPC BSPs)
35
36In addition, the following standard autoconf options are frequently
37used when configuring RTEMS installations:
38
39        --prefix=INSTALL_DIRECTORY
40        --program-prefix=
41
42By default, inline routines are used instead of macros where possible.
43Macros can be selected using the --disable-inlines option.  [NOTE:
44Some APIs may not support macro versions of their inline routines.]
45
46By default, the RTEMS POSIX 1003.1b interface is built for targets that support
47it. It can be disabled with the --disable-posix option.
48
49By default, the RTEMS uITRON interface is built for targets that support
50it. It can be disabled with the --disable-itron option.
51
52By default, the RTEMS networking support is built for targets which
53support it.  It can be specifically disabled for those targets
54with the --disable-networking option.
55
56By default, the RTEMS remote debugger server support is not built.
57It can be specifically enabled for the targets that support it.
58with the --enable-rdbg option. NB : the RTEMS networking support
59must be enabled to support the remote debugger server.
60
61By default, the RTEMS support of C++ is disabled.  It can be enabled
62with the --enable-cxx option. If the rtems++ C++ library is installed
63it will also be build.
64
65By default, the RTEMS test suites are NOT configured -- only the
66sample tests are built.  The --enable-tests will not configure
67the RTEMS test suite. The default speeds up the build
68and configure process when the tests are not desired.
69
70By default, RTEMS is built using arguments and build rules which are
71NOT compatible with gcc 2.7.2.2.  If using a gcc which supports the
72-specs option, then the --enable-gcc28 option may be used to enable
73this feature.  You should use the --enable-gcc28 option when using
74either the egcs source tree, testgcc snapshots, or gcc 2.8.0 or newer.
75If you --disable-gcc28, then you MUST  specify the location of the
76Standard C Library with the --enable-libcdir option.   [NOTE: These
77options are considered obsolete and may be removed in a future
78RTEMS release.]
79
80By default, multiprocessing is is not built.  It can be enabled
81for those BSPs supporting it by the --enable-multiprocessing option.
82
83By default, all bsps for a target are built. The bare BSP is not built
84unless directly specified. There are  two ways of changing this:
85
86  + use the --enable-rtemsbsp option which will set the specified
87    bsps as the default bsps, or
88  + set the RTEMS_BSP variable during make (see below).
89
90The --enable-rtemsbsp= option configures RTEMS for a specific target
91architecture.  Remember that the target specifies the CPU family while
92the BSP specifies the precise board you will be using. The following
93targets are supported:
94
95        (none)                  will build the host-based version on Linux,
96                                Solaris and HPUX.
97
98        a29k-rtems              only standalone, uses non-gnu compiler
99        arm-rtems
100        h8300-rtems
101        i386-rtems
102        i960-rtems
103        hppa1.1-rtems
104        m68k-rtems
105        mips-rtems
106        mips64orion-rtems
107        no_cpu-rtems
108        powerpc-rtems
109        sh-rtems
110        sparc-rtems
111        bare                    see notes
112       
113The cross-compiler is set to $(target)-gcc by default. This can be
114overridden by:
115
116  + using the --program-prefix option to configure to specify the
117    string which will prepended to the tool names.  Be sure to include
118    a trailing "-".  For example, to use a m68k-coff toolset, use the
119    --program-prefix=m68k-coff- option.
120
121To build, run make in the build directory. To specify which bsps to build,
122add the RTEMS_BSP="bsp1 bsp2 .." to the make command.  Specifying multiple
123BSPs to build only works from the top level build directory.
124
125Installation is done under $(prefix)/rtems.
126
127As an example, to build and install the mvme136 and dmv152 bsps for m68k do:
128
129        (path_to_rtems_src)/configure --target=m68k-rtems
130
131        make RTEMS_BSP="mvme136 dmv152"
132       
133        make install RTEMS_BSP="mvme136 dmv152"
134
135The sample tests are built by 'make all', do a 'make test' to build the full
136test suite.
137
1382.2 Build with Cygnus one-tree release
139
140To build and install RTEMS with the one-tree structure, just copy the rtems
141directory to the tree. The one-tree configure.in and Makefile.in has to be
142replaced with the RTEMS-aware versions. The build options are the same as
143for the standalone build.
144
1452.3 Target Dependent Notes
146
147bare:
148
149  1.  See the README in the bare bsp source directory. This should
150      contain all info you need.
151  2.  The bare bsp source contains a script to show how to build it.
152  3.  The configure flags must be used to get the bare bsp to work.
153      The --enable-bare-cpu-model and --enable-bare-cpu-cflags are the
154      only pieces of information. The module is usually a gcc module
155      such as m68302 or mcpu32. The flags are passed directly to gcc.
156      Use "" if more than one option is specified.
157
1583. To use the installed RTEMS library
159=====================================
160
161To use the installed RTEMS bsps to build applications, the application
162makefile has to include a bsp-specific makefile that will define the
163RTEMS variables necessary to find include files and libraries. The
164bsp-specific makefile is installed at
165
166        $(RTEMS_MAKEFILE_PATH)/Makefile.inc
167
168For the erc32 bsp installed at /usr/local/cross, the environment
169variable RTEMS_MAKEFILE_PATH would be set as follows to the
170following:
171
172/usr/local/cross/sparc-rtems/rtems/erc32/Makefile.inc
173
1744. Supported target bsps
175========================
176
177The following bsps are supported:
178
179host-based      : posix (on Linux, Solaris and HPUX)
180
181a29k            : portsw
182arm             : arm_bare_bsp armulator vegaplus
183c4x             : c4xsim
184h8300           : h8sim
185i386            : i386ex pc386 ts_386ex
186i960            : cvme961 i960sim rxgen960
187hppa1.1         : simhppa
188m68k            : dmv152 efi332 efi68k gen68302 gen68340 gen68360
189                  gen68360_040 idp mvme136 mvme147 mvme147s mvme162 ods68302
190                  mrm332
191no_cpu          : no_bsp
192mips            : p4600 p4650 (p4000 port with either R4600 or R4650)
193                  jmr3904 genmongoosev
194mips64orion     : (deprecated)
195                  p4600 p4650 (p4000 port with either R4600 or R4650)
196powerpc         : dmv177 eth_comm helas403 gen405 mbx8xx motorola_powerpc (covers
197                  most Motorola VMEbus and CompactPCI boards) ppcn_60x
198                  psim score603e
199sh              : gensh1 gensh2
200sparc           : erc32 erc32nfp leon1 leon2
201any             : bare
202
2035. Makefile structure
204=====================
205
206The makefiles have been re-organized. Most gnu-based bsps now use three
207main makefiles:
208    + custom/default.cfg,
209    + custom/bsp.cfg and
210    + compilers/gcc-target-default.cfg.
211
212Default.cfg sets the default values of certain common build options.
213
214Bsp.cfg set bsp-specific build options and can also override the
215default settings.
216
217Gcc-target-default.cfg contains the common gcc definitions. Some targets
218(a29k, no_cpu, and posix) still use the old structure.
219
2206. Adding a bsp
221===============
222
223The top-level configure.in has to be modified if a new target is added
224or if a new bsp is to be built by default. The additions required is
225basically to add which makefiles are to be created by configure and
226to add the target to the selection statement. To re-generate
227configure, autoconf-2.13 and automake-1.14 are needed.
228
2297. Tested configurations
230========================
231
232All gnu-based bsps have been built on Linux.
233The native (posix) ports have been built and run only on Linux.
234
235The following configurations have NOT been tested:
236
237    + Anything on Nextstep, HPUX and Irix.
238    + The a29k port.
239
2408. Pre-requisites
241=================
242
243Gawk version 2 or higher.
244GNU make version 3.72 or higher.
245Bash.
246gcc version ???
247
248TODO
249====
250
251The install-if-change script requires bash. On Solaris systems, this should
252be changed to ksh, since ksh is provided with Solaris (bash not).
253
254A fairly recent version of gawk is needed to build RTEMS. This should be
255changed so that a plain vanilla awk also works. [NOTE: This dependency
256should disappear when the "gcc 2.8 -specs" is finished.]
257
258'make install' should only install necessary files, not the full
259PROJECT_RELEASE directory as now.
260
261Posix port on Solaris-2.5 fails due to undefined built-in functions
262(gcc-2.7.2, might be my installation).
263
264Improve support for 'make CFLAGS=xxx'.
265
Note: See TracBrowser for help on using the repository browser.