1 | @c |
---|
2 | @c COPYRIGHT (c) 1988-1999. |
---|
3 | @c On-Line Applications Research Corporation (OAR). |
---|
4 | @c All rights reserved. |
---|
5 | @c |
---|
6 | @c $Id$ |
---|
7 | @c |
---|
8 | |
---|
9 | @chapter Requirements |
---|
10 | |
---|
11 | A fairly large amount of disk space is required to perform the build of the |
---|
12 | GNU C/C++ Cross Compiler Tools for RTEMS. The following table may help in |
---|
13 | assessing the amount of disk space required for your installation: |
---|
14 | |
---|
15 | @example |
---|
16 | +------------------------------------+--------------------------+ |
---|
17 | | Component | Disk Space Required | |
---|
18 | +------------------------------------+--------------------------+ |
---|
19 | | archive directory | 35 Mbytes | |
---|
20 | | tools src unarchived | 150 Mbytes | |
---|
21 | | each individual build directory | 300 Mbytes | |
---|
22 | | each installation directory | 20-200 Mbytes | |
---|
23 | +------------------------------------+--------------------------+ |
---|
24 | @end example |
---|
25 | |
---|
26 | It is important to understand that the above requirements only address |
---|
27 | the GNU C/C++ Cross Compiler Tools themselves. Adding additional |
---|
28 | languages such as Fortran or Objective-C can increase the size |
---|
29 | of the build and installation directories. Also, the unarchived |
---|
30 | source and build directories can be removed after the tools are |
---|
31 | installed. |
---|
32 | |
---|
33 | After the tools themselves are installed, RTEMS must be built |
---|
34 | and installed for each Board Support Package that you wish |
---|
35 | to use. Thus the precise amount of disk space required |
---|
36 | for each installation directory depends highly on the number |
---|
37 | of RTEMS BSPs which are to be installed. If a single BSP is |
---|
38 | installed, then the additional size of each install directory |
---|
39 | will tend to be in the 40-60 Mbyte range. |
---|
40 | |
---|
41 | There are a number of factors which must be taken into |
---|
42 | account in oreder to estimate the amount of disk space required |
---|
43 | to build RTEMS itself. Attempting to build multiple BSPs in |
---|
44 | a single step increases the disk space requirements. Similarly |
---|
45 | enabling optional features increases the build and install |
---|
46 | space requirements. In particular, enabling and building |
---|
47 | the RTEMS tests results in a significant increase in build |
---|
48 | space requirements but since the test are not installed has |
---|
49 | no impact on installation requirements. |
---|
50 | |
---|
51 | The instructions in this manual should work on any computer running |
---|
52 | a UNIX variant. Some native GNU tools are used by this procedure |
---|
53 | including: |
---|
54 | |
---|
55 | @itemize @bullet |
---|
56 | @item GCC |
---|
57 | @item GNU make |
---|
58 | @item GNU makeinfo |
---|
59 | @end itemize |
---|
60 | |
---|
61 | In addition, some native utilities may be deficient for building |
---|
62 | the GNU tools. |
---|
63 | |
---|
64 | @section GNU makeinfo Version Requirements |
---|
65 | |
---|
66 | In order to build egcs 1.1b, gcc 2.9.x, or newer versions, the GNU |
---|
67 | @code{makeinfo} program |
---|
68 | installed on your system must be at least version 1.68. The appropriate |
---|
69 | version of @code{makeinfo} is distributed with @code{gcc}. |
---|
70 | |
---|
71 | The following demonstrates how to determine the version of @code{makeinfo} |
---|
72 | on your machine: |
---|
73 | |
---|
74 | @example |
---|
75 | makeinfo --version |
---|
76 | @end example |
---|
77 | |
---|