Now that we're doing slightly-off-topic discussions anyway, let me
ask a question I have:
On 24-Oct-2007, at 18:52 , Erik van Pienbroek wrote:
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.
Since I discovered that Dependency Walker can also give info about
WinCE programs and DLLs my life has become an awful lot simpler indeed!
But my one problem with it is that I haven't been able to find a way
to tell it "Don't look in \SYSTEM or \WIN32 or whatever the win32
standard DLL places are, but look _here_ in stead". And then, at
_here_, I would have a copy of the system directory from my Windows
Mobile device. This would make the output of Dependency Walker 100%
correct, in stead of 98% as it is now: if something is available on
your windows desktop machine but not on Windows Mobile it won't
complain.
Does anyone know of a way to make Dependency Walker do this?
--
Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma
Goldman
-------------------------------------------------------------------------
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
