If you use only the types of references that are included in the EXE or PKD files built by PocketBuilder (as described in “Which objects are copied to the executable file”), you do not need to do anything else to ensure that all objects get distributed: they are all built into the executable file or its dynamic libraries.
If you use the types of references described in the two previous sections (“Which objects are not copied to the executable file” and “Which objects are not copied to the dynamic libraries”), you must include the objects that were not found, using the methods that follow.
For graphic objects in BMP, ICO, or GIF files, you have two choices:
Distribute them separately
Include them in a PKR file, then build an executable file or dynamic PocketBuilder library that uses the resource file
Graphic objects in JPEG files cannot be included in a PKR file and must be distributed separately if they are not built into the executable file. Graphic objects in PNG files cannot be included in a PKR file or an executable file, and can only be used if they are distributed separately.
For DataWindow objects, you have two choices:
Include them in a PKR, then build an executable file or dynamic PocketBuilder library that uses the resource file
Build and distribute a dynamic library from the PKL that contains the DataWindow objects
All other objects (such as windows referenced only in string variables) must be included directly in a dynamic library.
Table 27-4 summarizes resource distribution possibilities.
Distribution method |
Graphic objects |
DataWindow objects |
Other objects |
|---|---|---|---|
As a separate file |
Yes |
No |
No |
In an executable or dynamic library that references a PKR |
Yes |
Yes |
No |
Directly in a dynamic library |
No |
Yes |
Yes |
