I've been seeing discussion of mingw32ce vs cegcc on this list for a
while, and not really paying attention. I've been using mingw32ce,
best as I can tell: /opt/mingw32ce/bin is on my path, and my Makefile
uses tools like ${CE_ARCH}-gcc after defining CE_ARCH=arm-mingw32ce.
I didn't put much thought into the choice: best as I can remember I
picked one two years ago and didn't reconsider because it worked. And
my stuff runs on winmo 6.1 too.
But now I want to use FindWindowEx and see that it's in a .def file on
the cegcc side of things but not on the mingw32ce side. Is cegcc the
future? Should I be switching? It doesn't appear that my code
compiles on the cegcc side. That may be just a matter of stricter
default compiler settings (tripping over redefinition of fd_set and
not finding the definition of swprintf, both errors on the mingw32ce
side too but not fatal), or could be more.
Anyway, I'd appreciate any advice you folks can give. Because working
around not having FindWindowEx may be more work than switching
toolchains. :-)
--Eric
--
******************************************************************************
* From the desktop of: Eric House, [EMAIL PROTECTED] *
* Crosswords 4.1.4 for PalmOS now ARM-native: xwords.sourceforge.net *
******************************************************************************
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
