iAnywhere.com - Using the UltraLite plug-in for CodeWarrior

Using the UltraLite plug-in for CodeWarrior

For embedded SQL and the static C++ API, 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 static C++ API UltraLite project, or if you alter a publication used in a static 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 must include. You should use ulpalmos.h from the h subdirectory of your SQL Anywhere Studio installation as your prefix file. The CodeWarrior plug-in sets this for you automatically.

If you have your own prefix file, it must include ulpalmos.h. The ulpalmos.h file defines macros required by UltraLite Palm applications and also sets CodeWarrior compiler options required by UltraLite.

Notes

Although the UltraLite plug-in does not configure your development environment for expanded mode, you can build expanded mode applications. For more information, see Building Expanded Mode applications.

If you are using either the ULSecureCerticomTLSStream or ULSecureRSATLSStream functions to implement encrypted synchronization, you must add ulrsa.lib or ulecc.lib to your CodeWarrior projects.