Changes between Version 10 and Version 11 of doc/app/palmbuild


Ignore:
Timestamp:
Nov 21, 2018 3:39:54 PM (6 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/palmbuild

    v10 v11  
    6969**However**, best practice would be to create  individual [wiki:doc/app/palm_config .palm.config files] for the different configurations, because this prevents from having to re-compile over and over again whenever modifying and working with just one single .palm.config file. Of course, {{{palmbuild}}} has to be executed for each configuration.\\
    7070
    71 == Options for manual {{{palmbuild}}} execution ==
    72 ||='''option''' =||='''default value''' =||='''meaning''' =||
    73 |-----------
    74 ||-c   ||default  ||Configuration identifier. Tells {{{palmbuild}}} which configuration file is to be used.  ||
    75 ||-v   ||---      ||Run in silent mode. Switches off most messages and prompts  ||
    76 
    7771\\
    7872== Automatic execution of {{{palmbuild}}} ==
     
    9387   palmbuild -v -c <ci> -r <ri>
    9488}}}
    95 where {{{<ci>}}} and {{{<ri>}}} are as given by the respective {{{palmrun}}} options.
     89where {{{<ci>}}} and {{{<ri>}}} are as given by the respective {{{palmrun}}} options. An additional option {{{-V}}} is added if the corresponding {{{palmrun}}} option {{{-V}}} has been set. For explanations of the internal options see the table below.
    9690
    97 {{{palmbuild}}} is never called by {{{palmrun}}} within a batch job, or by automatic calls of {{{palmrun}}} to generate restart jobs. Reasons are to avoid compilation within batch jobs (which may be very inefficient if the job runs on many cores), and because automatic restart runs should and can re-use the binaries that have been created by the initial run and are saved in the respective SOURCES_FOR_RUN folder.
     91{{{palmbuild}}} is never called by {{{palmrun}}} within a batch job, or by automatic calls of {{{palmrun}}} to generate restart jobs. Reasons are to avoid compilation within batch jobs (which may be very inefficient if the job runs on many cores), and because automatic restart runs should and can re-use the binaries that have been created by the initial run and are saved in the respective SOURCES_FOR_RUN folder. \\\\
     92
     93
     94== {{{palmbuild}}} user options ==
     95||='''option''' =||='''default value''' =||='''meaning''' =||
     96|-----------
     97||-c   ||default  ||Configuration identifier. Tells {{{palmbuild}}} which configuration file is to be used.  ||
     98||-v   ||---      ||Run in silent mode. Switches off most messages and prompts.  ||
     99
     100
     101== {{{palmbuild}}} internal options ==
     102||='''option''' =||='''default value''' =||='''meaning''' =||
     103|-----------
     104||-r   ||---      ||Run identifier, as specified with {{{palmrun}}} option {{{-r}}}.  ||
     105||-V   ||---      ||Do not compile sources for the SOURCES_FOR_RUN folder.   ||
     106
    98107
    99108