Changes between Version 4 and Version 5 of QuickStartUnix


Ignore:
Timestamp:
Feb 27, 2010, 7:38:55 PM (14 years ago)
Author:
becoulet
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QuickStartUnix

    v4 v5  
    9292== Writing the MutekH configuration ==
    9393
     94=== Standalone configuration file ===
     95
    9496Our configuration file is named `hello/config_emu`.
    9597Details about configuration file is explained later.
     
    120122}}}
    121123
    122 The complete configuration files are available here: [source:trunk/mutekh/examples/hello/config_emu] and [source:trunk/mutekh/examples/hello/config_emu64]. You must choose the right one depending on your host operating system and architecture.
     124The complete configuration file is available here: [source:trunk/mutekh/examples/hello/config_emu].
    123125
    124126Have a look to the BuildSystem page for more information about configuration system and configuration file format.
    125127The [http://www.mutekh.org/www/mutekh_api/ MutekH API reference manual] describes all available configuration tokens.
     128
     129=== Generic configuration file ===
     130
     131The flat and standalone configuration file described above
     132is specific to the target emu architecture, GNU/Linux host
     133operating system and x86 32bits processor.
     134
     135It's possible to write a more generic configuration file which
     136relies on common files to target more platforms.
     137
     138The complete generic configuration file is available here: [source:trunk/mutekh/examples/hello/config].
    126139
    127140== Compiling the application along with MutekH ==
     
    132145}}}
    133146
    134 Once the compilation process has finished, the executable binary is available:
     147or to use the generic configuration file:
    135148{{{
    136 kernel-emu-x86-emu.out
     149make CONF=examples/hello/config BUILD=emu-linux-x86
    137150}}}
     151
     152This allow targeting other emu platforms like MacOs X (darwin) and x86_64 processors
     153and other hardware platforms.
     154
     155Once the compilation process has finished, the executable binary is available.
    138156
    139157== Execution ==