On Tuesday 29 December 2009 08:34:12, Danny Backx wrote:
> On Mon, 2009-12-28 at 18:00 +0100, Vincent Torri wrote:
> > On Mon, 28 Dec 2009, Pedro Alves wrote:
> > > I also see that you set -D_WIN32_IE=0x0400 in the Makefile.  I wish
> > > people would stop doing that.  _WIN32_IE is not meant for CE
> > > usage.  If you do need it, it's a bug in the w32api headers that
> > > needs fixing (to expose functions/macros under _WIN32_WCE).
> 
> Yes this is a bug.
> 
> An example : the include/commctrl.h in cygwin's CVS contains :
> #if _WIN32_IE >= 0x400
> #define TB_GETOBJECT    (WM_USER+62)
> #define TB_GETBUTTONINFOW       (WM_USER+63)
> #define TB_SETBUTTONINFOW       (WM_USER+64)
> #define TB_GETBUTTONINFOA       (WM_USER+65)
> 
> As a consequence, so does our version of that file. Our w32api/include
> directory has a few of those :
> pavilion: {394} fgrep _WIN32_IE *.h | wc -l
> 232
> pavilion: {395} 
> 
> Fixing these is not rocket science, but it is not something you'll want
> to do without a serious round of testing. It's easy to make mistakes in
> such editing sessions.

Of course, you don't have to do it all in one go.  I don't expect
applications to make use of the entire Win32 API!  If you
don't report the specific problems that affect you, they'll
never get fixed.  But if everyone reports them, after a few
rounds, we'll have most of the _WIN32_IE checks that matter for
CE fixed.  It may well be that we don't have to fix the whole >200
sites... You've already identified TB_GETOBJECT and friends above.  We
could start with fixing that.  At some point, there won't
be much else to fix and we'll be golden.

-- 
Pedro Alves

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to