Changes in README.md [1a4ec93f:8f059b5] in mainline


Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed

  • README.md

    r1a4ec93f r8f059b5  
    2626## Portability
    2727
    28 HelenOS runs on eight different processor architectures and machines ranging
     28HelenOS runs on seven different processor architectures and machines ranging
    2929from embedded ARM devices and single-board computers through multicore 32-bit
    3030and 64-bit desktop PCs to 64-bit Itanium and SPARC rack-mount servers.
    … …  
    5151dependencies and try again.
    5252
    53 As an example, here are some of the packages you will need for Ubuntu 16.04:
     53As an example, here are some of the packages you will need for Ubuntu 12.10 (may be out of date):
    5454
    5555```
    56 $ sudo apt install build-essential wget texinfo flex bison dialog python-yaml genisoimage
     56$ sudo apt-get install build-essential libgmp-dev libmpfr-dev ppl-dev libmpc-dev zlib1g-dev texinfo libtinfo-dev xutils-dev flex bison
    5757```
    5858
    … …  
    7070### Configuring the build
    7171
    72 Since the summer of 2019, HelenOS uses the Meson build system.
    73 Make sure you have a recent-enough version of Meson and Ninja.
    74 The safest bet is installing both using `pip3` tool.
     72Go back to the source root of HelenOS and start the build process:
    7573
    76 ```sh
    77 $ pip3 install ninja
    78 $ pip3 install meson
     74```
     75$ cd ..
     76$ make PROFILE=amd64
    7977```
    8078
    81 Meson does not support in-tree builds, so you have to create a directory
    82 for your build. You can have as many build directories as you want, each with
    83 its own configuration. `cd` into your build directory and run `configure.sh`
    84 script which exists in the source root. `configure.sh` can be run with a profile
    85 name, to use one of the predefined profiles, or without arguments for interactive
    86 configuration.
    87 
    88 ```sh
    89 $ git clone https://github.com/HelenOS/helenos.git
    90 $ mkdir -p build/amd64
    91 $ cd build/amd64
    92 $ ../../helenos/configure.sh amd64
    93 ```
     79Now HelenOS should automatically start building.
    9480
    9581Note: If you installed the toolchain to a custom directory, make sure `CROSS_PREFIX`
    9682environment variable is correctly set.
    9783
    98 Once configuration is finished, use `ninja` to build HelenOS.
    99 Invoking `ninja` without arguments builds all binaries and
    100 debug files, but not bootable image. This is because during
    101 development, most builds are incremental and only meant to check
    102 that code builds properly. In this case, the time-consuming process of
    103 creating a boot image is not useful and takes most time. This behavior
    104 might change in the future.
    105 
    106 In case you want to rebuild the bootable image, you must invoke
    107 `ninja image_path`. This also emits the name of the bootable image into the
    108 file `image_path` in build directory.
    109 
    110 ```
    111 $ ninja
    112 $ ninja image_path
    113 ```
    114 
    115 Now HelenOS should automatically start building.
    116 
    11784### Running the OS
    11885
    119 When you get the command line back, there should be an `image.iso` file in the build
     86When you get the command line back, there should be an `image.iso` file in the source
    12087root directory. If you have QEMU, you should be able to start HelenOS by running:
    12188
Note: See TracChangeset for help on using the changeset viewer.