Oops...
I realize now that the fix for compiling for windows when UNICODE is defined is in my
TODO list.
I was waiting for it to be fixed in the main code, to minimize the changes from the
original code.
In the total, there are only a dozen changes to the code in "os.c". I can also make a
patch, if that is desired.
Regards,
~Nuno Lucas
=== On 2004-03-17, Nuno Lucas wrote ===
>Just a litle correction....
>
>=== On 2004-03-17, Andrew Francis wrote ===
>...
>>
>>Regardless, I'd start by looking at the sqlite ports to Windows CE /
>>PocketPC. From memory, there are a couple around. Windows CE provides
>>only Unicode versions of the Win32 functions, so generally WinCE code
>>has to be TCHAR/Unicode 'clean.'
>>
>
>All WinCE ports I know of (including the one I try to maintain - sqlite-wince.sf.net)
>just wrap the OS specific functions to work with the Unicode only available Win32 API
>functions (and a few tweaks to make synchronization work).
>The sqlite API is unchanged, just the UTF8 is enabled by default.
>I don't see any advantage in creating a Unicode specific sqlite API, as this can be
>done by a simple wraper made by the user (that all C++ programmers out there would
>make, anyway by creating their object encapsulation to sqlite C API).
>The only thing I can say about my WinCE port is that it compiles on normal windows,
>too, reverting to the original sqlite source code (compiling with or without UNICODE
>defined).
>
>For the original poster:
>If you want a hint on how to do your wraping, see the help on mbstowcs/wcstombs
>functions of the C runtime, or MultiByteToWideChar/WideCharToMultiByte in the Win32
>API.
>
>Best regards,
>~Nuno Lucas
>
----------------------------------------------------------------------
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
