pilrc - A resource compiler for the Palm Computing Platform

pilrcui - A graphical editor for PalmOS resource files

pilrc [ -L LANGUAGE ] [ -I INCLUDE PATH ] [ -D MACRO(=VAL) ] [ -R RESFILE ] [ -H INCLUDE PATH ] [ -ro ] [ -q ] [ -V ] [ -Fh ] [ -Fj ] [ -F5 ] [ -Fg ] [ -Fkm ] [ -Fkt ] [ -LE32 ] [ -allowEditID ] [ -o OUTPUTPATH ] file.rcp [ output-path ]

pilrcui [ -L LANGUAGE ] file.rcp

The information in this man page is an extract from the full documentation of the PalmOS resource compiler, and is limited to the meaning of the options.

For complete documentation on the pilrc and pilrcui programs, please see the HTML documentation included in this package.

pilrc takes the following list of command line options: Generate resource files for target language, LANGUAGE. Search INCLUDE PATH when looking for include or bitmap files. NOTE: multiple paths be repeating the -I option. Define a pre-processor symbol with an optional value. The macros defined with the -D option can be referenced in #ifdef statements in the resource file for conditional compilation. NOTE: if no value is specified, the symbol will given the value of 1. Output a .res file specifying all the resources emitted by PilRC. Output a .h file containing auto-generated resource item IDs for resource items that were defined without an ID previously. NOTE: If -H is not specified then undefined IDs are considered errors. Output a single .ro file in PRC format containing all the generated resources, instead of a collection of .bin files. Less noisy output, for you minimalists. Generate M$ (VS-style) warning/error output (default is GNU-style). Use Hebrew font widths for AUTO width calculations. Use Japanese font widths for AUTO width calculations. Use Chinese (Big5) font widths for AUTO width calculations. Use Chinese (GB) font widths for AUTO width calculations. Use Korean font widths for AUTO width calculations (Hanme font) Use Korean font widths for AUTO width calculations (Hantip font) Allow the use of edit menu ID values (10000-10007 inclusive). Generate Little Endian 32 bits compatible resources (ARM, NT) Alternative way of specifying an output path (below). Input file describing the resources to be emitted. Directory where .bin files should be generated, or name of the file to generate containing all the generated resources.

The resources generated are output as a collection of .bin files or as resources within a PRC file, depending on whether -ro is given: Without -ro, each resource is written as a separate file in the output path directory. Each output filename is constructed by appending the hexcode resource ID and .bin to the four character resource type. With -ro, the resources are written to a single file, with the name given by the output path. The extension .ro is added if the name has no extension. If no output path has been given, a filename is constructed from the input filename by replacing .rcp with .ro (or appending .ro if the input filename does not end in .rcp).

    pilrc myprogram.rcp
    pilrc -I ../resources -L FRENCH myprogram.rcp
    pilrc -I ../resources -L BIG5 -F5 -R myprogram.res myprogram.rcp output
    pilrc -ro -o myresoures.ro myprogram.rcp
    pilrc -ro myprogram.rcp

The following describes some basic characteristics of resource files. For more complete information, see the HTML documentation included with this package:

example: kFoo example: O (may contain normal C style character escapes) example: Click Me (may contain normal C style character escapes) PilRC will concatenate strings on separate lines example: Now is the time for all good \ men to come and aid of their country defined constant or simple arithmetic expression. Valid operators are +, -, * and /. Precedence is left to right, unless changed with the use of parenthesis. NOTE: Math calculations are integer based. example:

    23
    12+3+1
    12*(2+3)

 Previous items width.

Single line comments begin with //.

Block comments exist between the /* and */ tokens.

Note: // comments within the definition of objects are treated as errors.

The .rcp file may contain #include directives. This allows a programmer to have one header file for their project containing pre-defined resource IDs. Source code can reference the symbols as can PilRC.

PilRC understands three include file formats.

  #define <Symbol.i><Value.n>

  <Symbol.i> equ <Value.n>

  package <PackageName>

  public class <ClassName> {
    public static final short <Symbol.i> = <Value.n>;
  }

Once defined, a symbol can be used in place of any number.

Note: #ifdef derivatives are ignored by PilRC.

This man page was generated by Stephen Zander <gibreel@debian.org> for the GNU/Debian Distribution.