On Wednesday 30 December 2009 19:38:29, Vincent Torri wrote: > > On Wed, 30 Dec 2009, Pedro Alves wrote: > > > On Tuesday 29 December 2009 06:33:30, Vincent Torri wrote: > > > >> about the linking, should I pass -Wl,--major-subsystem-version,4 and > >> -Wl,--minor-subsystem-version,20 ? > > > > I can't remember if this has any effect on dlls (IIRC, application > > user interface look different [menubar, etc.] if you specify an > > old subsystem version), but, any reason to limit this 4.2, instead > > of sticking to the default of 3.0? > > no real reason. We are in 2009, win ce 3.0 was released in 1999, 4.2.0 in > 2003. I don't think that there is a lot of embedded devices using win ce 3 > only.
If there's no reason, I'd say leave in the defaults. You never know what's out there. zlib builds fine with _WIN32_WCE set to 0x300, and so does src/mingw, and so do all the dlls we ship. > I can't remember if i really need win ce > 3.0 in the libraries i'm > porting. Other libs are irrelevant here though. You should be able to mix and match dlls with different subsystem-versions. (btw, I've got that zlib errno/GetLastError patch almost ready) -- 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
