On Mon, Nov 20, 2006 at 02:27:59PM +0000, Pedro Alves wrote: > Pedro Alves escreveu: > > Kevin O'Connor escreveu: > > > >> On Mon, Nov 20, 2006 at 01:18:21AM +0000, Pedro Alves wrote: > >> > >> > >>> I have never seen a WinCE < 3 machine, and I don't really know for sure > >>> what may be different there. > >>> Currently all the toolchain is built with CE 3 as the default (linker > >>> and headers). > >>> > >>> > >> I was looking at this a little further. It seems the mingw code is > >> calling GetCommandLine. However, that function was introduced in CE3:
Hi Pedro, I have confirmation that the app works on the WinCE 2.1 strongarm processor if we bypass the WinMainCRTStartup and explicitly call __gccmain from WinMain. As to a fix - I'm a bit confused by the current mingw crt1.c code. Why do we have WinMainCRTStartup call main() which then calls WinMain. Wouldn't it be simpler to have a dummy WinMain that calls main(). This way, the code doesn't have to scan all the command-line arguments if the application isn't interested in them. Also, what are the requirements in these files for 386 compatibility? It seems like there isn't that much overlap between between desktop windows and ce windows. I find the ifdefs to be hard to follow - in particular because there are a number of ifdefs (MSV_CRT, UNDER_CE, COREDLL) and it isn't clear which are actually in effect on CE. I wonder if it be simpler to have a ce specific crt1.c file. Finally, is this something you're willing to fix? -Kevin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
