Changes between Version 4 and Version 5 of PortingSoftware


Ignore:
Timestamp:
2014-05-12T12:16:57Z (10 years ago)
Author:
Vojtech Horky
Comment:

Update link to coastline

Legend:

Unmodified
Added
Removed
Modified

  • PortingSoftware

    v4 v5  
    4343== Coastline ==
    4444
    45 Currently, Coastline is hosted as a separate Git [https://github.com/vhotspur/coastline repository on GitHub].
    4645
    4746Coastline is a set of scripts that allows the developer porting software to HelenOS capture the porting process in a reasonable way.
    … …  
    5049Use of Coastline means that the porting process is reproducible and it also allows to factor our common routines.
    5150
     51Coastline is hosted as a Bazaar repository that can be [source:coastline browsed on-line].
     52To clone the repository, issue the following command:
     53
     54{{{
     55brz branch bzr://helenos.org/coastline
     56}}}
     57
    5258When the developer uses the Coastline, he is working with 3 directories.
    5359The first one is the directory with Coastline checkout, in the scripts referred to as `HSCT_HOME`.
    5460Second one is the build directory where the building happens.
    5561And the last one is directory with HelenOS sources (`HSCT_HELENOS_ROOT`).
     62
     63The following text assumes that following variables point to different directories where you have check-out of the Coastline and HelenOS mainline and also a build directory.
     64
     65{{{
     66HSCT_HOME=~/helenos/coastline
     67HSCT_HELENOS_ROOT=~/helenos/mainline
     68BUILD_DIR=~/helenos/coast-build-ia32
     69}}}
    5670
    5771The build directory needs to be initialized first.
    … …  
    6276
    6377{{{
    64 $HSCT_HOME/hsct.sh init /path/to/HelenOS/source/tree
     78cd $BUILD_DIR
     79$HSCT_HOME/hsct.sh init $HSCT_HELENOS_ROOT
    6580}}}
    6681
    6782If you specify a profile (e.g. `ia32`) as a third argument, the initialization would prepare the build directory for that profile.
    6883Specifying the word `build` as a last (fourth) argument would force a complete rebuild for the specified profile.
     84To avoid surprises from non-standard configuration, the recommended practice is to always forcefully rebuild the profile when initializing the directory:
     85
     86{{{
     87cd $BUILD_DIR
     88$HSCT_HOME/hsct.sh init $HSCT_HELENOS_ROOT ia32 build
     89}}}
    6990
    7091Once the directory is initialized, the user can build the ported software.
    … …  
    7293
    7394{{{
    74 hsct.sh build <package>
     95$HSCT_HOME/hsct.sh build <package>
    7596}}}
    7697
    … …  
    82103
    83104{{{
    84 hsct.sh install <package>
     105$HSCT_HOME/hsct.sh install <package>
    85106}}}
    86107
    … …  
    89110
    90111{{{
    91 hsct.sh archive <package>
     112$HSCT_HOME/hsct.sh archive <package>
    92113}}}
    93114