I don't know what compilers you people were using, and exactly what you managed to do.
I am using the Mingw32 version of cegcc (i.e. arm-wince-mingw32ce-gcc)
I tried to compile an example (using the IDE) - and I started with compilation errors 'cAlternateFileName not defined'. I added -DPLATFORM_WINCE to the compile options, and that went away.
This definition needs to be added automatically when WINCE is chosen as the platform.
Now I have
CtrlLib\RichTextView.cpp:458: error: 'PrinterJob' was not declared in this scope
I suggest that this function be #ifdef'ed out (and replaced with a stub) on WINCE.
Those are the only problems in the CtrlLib.
There are a few problems with the CtrlCore too.
In general - do these problems appear with other WinCE compilers?
Is anyone else using cegcc?
Any advice?
These are very good news. In fact, we planned full support for cegcc, even distributing U++ with it, but so far this has not gone anywhere (too much else to do).
If you would succeed here, the path would be open.
The only WinCE tests we did was with VS C++ 2005 compiler. I have succeeded to compile and run most of "examples" - it has looked a bit weird (we will need to make special chameleon branch for WinCE), but worked (with some crashing