Palm Component Implementation
A Piedmont component is compiled as
a shared library with the type
set to zpco. Create an empty CodeWarrior project,
called ParseServer in the ParseServer directory
you created earlier (see Figure 9-1, earlier in
this chapter). Change the project settings to correspond with those
listed. We assume the default Piedmont SDK and Metrowerks compiler
installations. These settings may vary based on your installation.
- Target Settings panel
- Target name
ParseServer- Linker
MacOS 68 Linker- Post Linker
PalmRez Post Linker- Output directory
{Project}PalmDebug
- Access Paths Panel
- User paths
{Project}C:\Program Files\AppForge\SDK\lib\PalmOS\DragonBall\CWPALM70{Project}..\common- System paths
{Compiler}Palm OS 3.5 SupportC:\Program Files\AppForge\SDK\includeC:\Program Files\AppForge\SDK\include\PalmOS
- 68K Target panel
- Project type
PalmOS Application- Filename
ParseServer.tmp
- C/C++ Language panel
Checked items (check additional options depending on your development needs)
Activate C++ Compiler- 68K Processor panel
- Floating Point
PalmOS- Checked items
4-Byte IntsPC Relative Strings
- PalmRez Post Linker panel
- Mac Resource files
ParseServer.tmp- Output file
ParseServer.prc- Type
zpco- Creator
TAGS- Transliteration
Palm OS 3.1 and later
Add the same files to this project as you did for the Windows
ParseServer project except for the IDX, MDX, DEF, INC, and IDL files.
You will also need to add the appropriate Piedmont libraries. These
libraries can be found in the
lib\PalmOS\DragonBall\CWPALM70 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access