Rev 150 | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 125 | decky | 1 | \chapter{Building HelenOS} |
| 150 | palkovsky | 2 | \section{Requirements} |
| 3 | To build HelenOS, the following build tools must be installed: |
||
| 4 | \begin{itemize} |
||
| 5 | \item GCC 4.1.1 + binutils 2.16.1 cross compiler environment for target platform |
||
| 6 | \item python 2.3 or higher |
||
| 7 | \item GNU make |
||
| 8 | \item mkisofs |
||
| 9 | \end{itemize} |
||
| 10 | The GNU build environment is best downloaded, compiled and installed |
||
| 11 | automatically using the shell scripts located in the |
||
| 12 | {\em kernel/contrib/toolchain} directory. |
||
| 125 | decky | 13 | |
| 150 | palkovsky | 14 | \section{Building} |
| 15 | HelenOS features a user friendly configuration system. Once |
||
| 16 | a {\em make} command is run from the {\em boot/} directory, a |
||
| 17 | {\em dialog} driven application is started and the developer is asked several |
||
| 18 | questions regarding build configuration parameters. The answers are saved |
||
| 19 | in the file {\em Makefile.config} in the boot/, kernel/ and uspace/ |
||
| 20 | directories and are automatically used for each subsequent build. |
||
| 21 | |||
| 166 | jermar | 22 | In order to modify the parameters, the user should change to the particular subsystem |
| 23 | directory and type {\em make config}. When the build configuration parameters |
||
| 24 | are changed, the whole subsystem should be completely rebuilt. The |
||
| 25 | configuration system offers to do this automatically for the user. |