[Python-Dev] Status of MS Windows CE port

["Martin v. Löwis"]

>> Please don't. Whether or not _UNICODE is defined should have no effect.
> 
> Well, currently it does make a difference. Simple example: CreateFile().

It's not so simple: Python doesn't actually call CreateFile, AFAICT
(well, it does, in _msi.c, but I hope you aren't worried about that
module on CE).

> One 
> of the parameters is actually documented at LPCTSTR, which is a TCHAR string. 
> That means that under CE, CreateFile(), which is actually a macro, resolves 
> to CreateFileW and the existing code that passes a char-string doesn't work.

True, but irrelevant: Python doesn't actually use CreateFile. Instead,
it calls both CreateFileA and CreateFileW (in posixmodule.c).

> VS2005 works really good with CE5 and later. My problem here is that I can't 
> provide a projectfile that suits everyone, because different devices have 
> different SDKs and each configuration/SDK/CPU is another entry in that file. 
> Further, the SDKs or devices differ in what they support, the platform CE as 
> such doesn't exist.

Hmm. And you *can* provide an SCons file that supports all the SDKs?

Regards,
Martin