[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can specify the database header attributes which appeared in an old-style build-prc command line along with the kind of project being built in this clause:
project-kind [ type ] { dbname crid miscellaneous... } |
This clause must appear exactly once, and must be first in the file,
before any other clauses. dbname, crid, and type
specify the database's name, creator id, and type. Except when
project-kind is database
, type can be omitted and a type
suitable for the project kind will be used. project-kind controls
the processing of the bfd executable, and should be one of the following:
app
application
appl
.
Code and data sections in the bfd executable are converted into Palm OS
code
, data
, and rloc
resources, and code #0
and pref #0
resources are synthesised.
glib
GLib
. Code and
data sections in the bfd executable are converted into GLib code
,
data
, and rloc
resources.
syslib
libr
.
Code sections in the bfd executable are converted into libr
code resources. Since system libraries typically don't have their
own global data, data sections in the bfd executable will produce a
warning rather than being converted, unless you also use the data
miscellaneous flag.
hack
HACK
. All bfd
executables given should be marked as stand-alone code sections, and any
data sections or extra code sections present will elicit warnings from
build-prc (see section 3.4 Stand-alone code resources).
database
The database name and creator id must come first within the braces, and may be followed by any number of the following, in any order:
read-only
appinfo-dirty
backup
ok-to-install-newer
reset-after-install
copy-prevention
stream
hidden
launchable-data
recyclable
bundle
modification=num
modnum=num
modno=num
version=num
stack=size
pref #0
resource request size
bytes of stack space. By default, 4K is requested.
data
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |