[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
build-prc [ -l ] [ -L ] [ -t type ] prcfile app-name crid file... build-prc [ -o file | --output file ] [ -a file | --appinfo file ] [ -s file | --sortinfo file ] [ -l ] [ -L ] [ -H | --hack ] [ -t type | --type type ] [ -c crid | --creator crid ] [ -n name | --name name ] [ -m num | --modification-number num ] [ -v num | --version-number num ] [ --read-only ] [ --appinfo-dirty ] [ --backup ] [ --ok-to-install-newer ] [ --reset-after-install ] [ --copy-prevention ] [ --stream ] [ --hidden ] [ --launchable-data ] [ --recyclable ] [ --bundle ] [ -z n | --compress-data n ] [ --no-check-header ] [ --no-check-resources ] [ --no-check ] file... |
build-prc
reads resources from the input files given and
combines them into one output Palm OS .prc resource data file. There are
two styles of build-prc command line: in the old style, the first three
non-option arguments describe the output file, and input files don't start
until the fourth argument. In the new style, all non-option arguments
are input files. An invocation is new-style if the first file argument
does not have a .prc extension or if the -o
option is used.
Input files are identified by their extension:
fname.def
typennnn.bin
typennnn.progname.grc
type #nnnn
resource, where nnnn is in hexadecimal.
fname.prc
fname.ro
.prc
format. The contents of all the
resources in a resource database are copied to the output database.
(The information in the input database's header--name, creator, flags,
etc--is entirely ignored.)
progname
.disposn
or a .trap
section,
its .text
section is converted to a stand-alone code resource
accordingly (see section 3.4 Stand-alone code resources). Otherwise, its code and data
sections are converted to resources according to a definition
file, or, if there is no definition file, as if the application
project kind was specified.
By default, build-prc
uses its first non-option argument as
the filename for its output .prc file. In an old-style command line,
prcfile is used as is. In a new-style command line, the output
filename is formed by removing the extension, if any, from the first
file argument and appending `.prc'.
-o file
--output file
-a file
--appinfo file
-s file
--sortinfo file
-l
-L
-H
--hack
-t type
--type type
Note that this affects only the type recorded in the database header; in particular, it does not change build-prc's notion of the kind of project being generated (see section project kinds), nor does it influence resource checking. If you do not want the database to be checked as if it is an application, you must either tell build-prc what it really is, by using a definition file or one of the options listed above, or, as a last resort, suppress resource checking entirely.
-c crid
--creator crid
-n name
--name name
-m num
--modification-number num
-v num
--version-number num
--read-only
--appinfo-dirty
--backup
--ok-to-install-newer
--reset-after-install
--copy-prevention
--stream
--hidden
--launchable-data
--recyclable
--bundle
--readonly
, etc).
-z N
--compress-data N
--no-check-header
--no-check-resources
By default, build-prc will check for these resources and emit diagnostics accordingly, which helps you detect mistakes such as the omission of a bfd executable from the build-prc invocation.
--no-check
--no-check-foo
options listed above.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |