Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.0 » UltraLite - C and C++ Programming » Application Development » Developing UltraLite applications for Windows Mobile


Introduction to Windows Mobile development

For a list of supported host platforms and development tools for Windows Mobile development, and for a list of supported target Windows Mobile platforms, see Supported platforms.

You can test your applications under an emulator on most Windows Mobile target platforms.

Preparing for Windows Mobile development

Microsoft eMbedded Visual C++ can be used to develop applications for the Windows Mobile environment. This development environment is available from Microsoft as part of eMbedded Visual Tools.

You can download eMbedded Visual C++ from the Microsoft Developer Network at [external link]

Applications targeting Windows Mobile should use the default setting for wchar_t and link against the UltraLite runtime libraries in install-dir\ultralite\ce\arm.50\lib\.

A first application

A sample eMbedded Visual C++ project is provided in the samples-dir\UltraLite\CEStarter directory. The workspace file is samples-dir\UltraLite\CEStarter\ul_wceapplication.vcw.

When preparing to use eMbedded Visual C++ for UltraLite applications, you should make the following changes to the project settings. The CEStarter application has these changes made.

  • Compiler settings:
    • Add $(SQLANY11)\SDK\Include to the include path.
    • Define appropriate compiler directives. For example, the UNDER_CE macro should be defined for eMbedded Visual C++ projects.
  • Linker settings:
    • Add "$(SQLANY11)\ultralite\ce\processor\lib\ulrt.lib"

      where processor is the target processor for your application.

    • Add winsock.lib.
  • The .sqc file (embedded SQL only):
    • Add ul_database.sqc and ul_database.cpp to the project
    • Add the following custom build step for the .sqc file:
      "$(SQLANY11)\Bin32\sqlpp" -q $(InputPath) ul_database.cpp
    • Set the output file to ul_database.cpp.
    • Disable the use of precompiled headers for ul_database.cpp.

Choosing how to link the runtime library