To reference the UltraLite header files and library it is convenient to create a user-defined build setting set to the location
of the SQL Anywhere installation directory. For example, set SQLANY_ROOT to /Applications/SQLAnywhere12. To create this setting, open the project editor's Build pane and select Add User-Defined Setting and enter the name and value.
Both Mac and iPhone UltraLite clients require that the public keys used for end-to-end encryption (i.e. provided to the e2ee_public_key stream parameter) must be encapsulated in a PEM encoded X509 certificate (as opposed to a PEM public key file). See e2ee_public_key.
The following encryption standards are not supported:
The Xcode debugger (GDB) has support for stepping through and breaking on longjmp() calls. Applications typically do not use longjmp, but the UltraLite runtime library does internally (sometimes, when an error is signalled, for instance). This may cause
problems when tracing through application code and stepping over UltraLite calls. If you step over an UltraLite call and get
an error from the debugger: Restart the program, set a breakpoint after the problematic line and, instead of stepping over
the problematic line, use the Continue command - this will have the same effect because the debugger will stop at the following breakpoint, but should avoid problems
related to longjmp calls. The most likely place to encounter this is when using OpenConnection() to open an existing database or determine that the database doesn't exist (an error is signalled when the database doesn't