cancel
Showing results for 
Search instead for 
Did you mean: 

Problem compiling app for iOS when changing from 12.0.0 to 12.0.1 - Unicode API no longer available

Former Member
1,645

Problem compiling app for iOS when changing from 12.0.0 to 12.0.1 - Unicode API no longer available

The UltraLite headers that are included in an iOS application have changed from 12.0.0 to 12.0.1. My application uses APIs and types that are defined under this condition: #ifdef UL_WCHAR_API . However, upgrading the version, and without changing anything else, UL_WCHAR_API is no longer defined, and the API and type definitions are no longer accessible. Trying to force the definition creates other problems such as ambiguous definitions, etc. Has anyone else had this problem? Is there anything we can do to safely enable this define?

Running on MacOSX Snow Leopard 10.6.7, XCode 4.2, iOS SDK 5.0

Thanks in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

The WCHAR (2-byte UCS-2/UTF-16) API is only supported on Windows platforms (where wchar_t is 2 bytes). The intention is that UTF-8 is used on iPhone.

Having said that - can you explain why you are using the wide APIs?

We have now added UTF-16 APIs on iOS for streaming character data to and from the database - available in the next EBF (12.0.1.3713 or later). The APIs are:

ULPreparedStatement::AppendParameterStringChunk ULResultSet::GetStringChunk ULResultSet::AppendStringChunk