Re: C++ dlls not loading with WM 6, worked with WM5.0

I'd say, "Compiled for the wrong target processor." You can use the
depends.exe program that comes with Visual Studio to look at the EXE (and
any of the DLLs that are statically linked). Verify that the right
processor is indicated. Since WM5 and WM6 both are running the same base
version of the Windows CE OS, I don't see how this could be anything other
than an improperly-built EXE or you linking with an import library for
something that doesn't exist on the new target device.

Paul T.

"Vishal" <Vishal@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:22BA74B7-C8FB-4DAE-909A-15638CDF6DF5@xxxxxxxxxxxxxxxx
Hi,

I need to build C and C++ libs and dlls that are linked in to by other
applications.
The C++ libraries link in the C libraries.

I have those built for Windows Mobile 5.0 and working fine.
I built the libraries for Windows Mobile 6, and am having trouble running
C++ applications that link in the libraries dynamically.
When I try to run a C++ application with dynamic linking from VS2005, I
get
a dialog box with message 'Unable to start program. No process is on the
other end of the pipe.'
C applications linked dynamically run fine.

So I wrote a small app that directly tried to load the libraries using
LoadLibrary(), and while it is able to load the C dll, it fails to load
the
C++ dll with error code 193: ERROR_BAD_EXE_FORMAT.
On the same Windows Mobile 6 PDA, when I try to load the dlls built for
Windows Mobile 5.0, I see the same behavior, i.e. failure to load the C++
dll, though the C dll loads just fine.

When I run the same app rebuilt for Windows Mobile 5.0, it is able to load
successfully the dlls built for Windows Mobile 5.0 [C and C++ dlls].
As expected, when I try to load the dlls built for Windows Mobile 6, I get
error code 1150: ERROR_OLD_WIN_VERSION

Any ideas on what I am doing wrong? Am I building my libraries
incorrectly,
or do I need some run time dlls on the Windows Mobile 6 PDA?

Thanks in advance,
-Vishal


.

Relevant Pages

  • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
    ... all the dependent DLLs (and all their dependent DLLs and all their ... DLL, though, this triggers the OS to actual load and link that DLL...hence, ... if your libraries are accessed almost immediately and ... As noted, though, most OSes out there are anything but "toolmaker's view" ...
    (alt.lang.asm)
  • Re: static library and dynamic library
    ... Also the code of the library will load into the program. ... yeah, at link time, all the code and data from the library goes into the binary, which is part of why using lots of static libs tends to produce large binaries... ... so, the loader will also grab the libraries, and resolve the addresses to the addresses in the library. ... in windows, however, DLLs are typically fixed-address to allow sharing. ...
    (comp.lang.c)
  • Re: Mex vs. Generic DLLs
    ... and only load the appropriate libraries ... I'd have to load the ... to dynamic libraries. ... The overhead of actually finding, opening, parsing, etc. multiple DLLs ...
    (comp.soft-sys.matlab)
  • Re: Memory limit reached with Windows Mobile
    ... If we load DLLs then Data, we can load 12 Mb of DLLs then 13 Mb of ... All native DLLs get loaded ... over 12,85 Mb of VirtualMemory, and that we can't load any Native ...
    (microsoft.public.pocketpc.developer)
  • Re: Memory limit reached with Windows Mobile
    ... I do understand what a test is, and I do understand how memory management ... ctacke: re-read Patrick's questions, ... 1- Load the same DLL over and over. ... Loading native DLLs takes at least 64k each. ...
    (microsoft.public.pocketpc.developer)