UltraLite Embedded SQL User's Guide
  Developing UltraLite Applications for the Palm Computing Platform
    Developing UltraLite applications with Metrowerks CodeWarrior

Using the UltraLite plug-in for CodeWarrior

The UltraLite plug-in for CodeWarrior integrates the UltraLite preprocessing steps (running the UltraLite generator and, for embedded SQL applications, running the SQL preprocessor) into the CodeWarrior compilation model. It ensures that the SQL preprocessor and UltraLite generator run when required.

If you change the UltraLite project name, or if you change the generated database name, you should delete the UltraLite Files folder. This forces regeneration of the generated files. To avoid filename collisions, do not use a generated database name that is the same as the .sqc file name.

If you change a SQL statement in a C++ API UltraLite project, or if you alter a publication used in a C++ API project, you must manually touch the dummy.ulg file to prompt the UltraLite generator to run.

For an overview of the tasks the plug-in carries out, see Configuring development tools for static UltraLite development.

Using prefix files 

A prefix file is a header file that all source files in a Metrowerks CodeWarrior project include. You should use ulpalmXX.h, where XX indicates the version of the Palm SDK you are using, from the h subdirectory of your SQL Anywhere Studio installation directory as your prefix file. The CodeWarrior plug-in sets this for you automatically.

If you have your own prefix file, it must include ulpalmXX.h. The ulpalmXX.h file defines macros required by Palm applications, such as the UL_PALMOS_SDK macro (which is set to the version of the Palm OS in use) and the UNDER_PALM_OS macro.