Hi, Op woensdag 24-10-2007 om 18:44 uur [tijdzone +0200], schreef Danny Backx: > > There is a utility which I would like to use (very much), but whenever I > > try to run it, I get "File is not a valid Windows CE application". > I've seen this type of message myself from applications compiled with > cegcc too, when there's something wrong with the *.def file from which > we create the lib*.a file that ends up linking our application to a DLL. > > If the DEF file defines an API that isn't in the DLL on your WinCE > device, then any application that accesses this API will provide this > message at startup. My best guess is that the Windows CE runtime loader > (which "connects" the DLLs) detects this situation and issues this > error.
I've also seen this situation several times. To find out what was going wrong I've used a tool called 'dependency walker'. With this program you can open a .exe (or .dll) file and you get to see all the dependent .dll's of this file including a list of functions imported by the file. If a imported function could not be resolved, you can easily see what functions could not be resolved. This tool is a Win32 program, but it can open WinCE .exe/.dll files without any problems. This program can also be run under Linux through Wine. Regards, Erik van Pienbroek ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
