WinCELauncher.exe build successfully but can not be started because one of the required components is missing.

[Alexander Genne]

Hi,
we can successfully build the WebKit but when trying to start the
WinCELauncher.exe an error message box pops up containing the message
that one of the required components is missing.
Can anyone help us out here?
Thank you in advance
Alex

[Rodney Dowdall]

Hello Alex

You can try an application by the name of InspectExe
(http://www.silurian.com/inspect/index.htm). It will tell you what your
application is dependant on. In my experience it is usually the
msvcr80.dll, msvcr80d.dll, msvcr90.dll, or msvcr90d.dll. Depends on what
version you are building.

Thanks,
Rodney

Rodney Dowdall
Crank Software Inc.
Office: 613-595-1999 ext. 513
Online: www.cranksoftware.com
Check out: Crank Software’s Blog
 
There is a better way to build user interfaces for embedded devices.
Download a 30 day evaluation of Crank Storyboard Suite today!

--
You received this message because you are subscribed to the Google Groups
"Windows CE WebKit" group.
To post to this group, send email to wince...@googlegroups.com.
To unsubscribe from this group, send email to
wincewebkit...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/wincewebkit?hl=en.

[Patrick Gansterer]

Hi,

did you have a look at the exe with depends.exe? Did you copy all required files to the device (MSVRT.dll)?

- Patrick

[Alexander Genne]

Hello Rodney, hi Patrick,
Thank You for your help, the reason was the lack of the files
msvcr90.dll, or msvcr90d.dll.
Now the applications starts and I can see an empty screen. I realized
that a homeUrl can be defined in the commandline. Doing so it seems
that the WebView is doing something, but at the end there is an empty
screen again. Is it possible to debug?
Thanx again
Best Regards
Alex

On Nov 14, 9:29 pm, "Rodney Dowdall" <rdowd...@cranksoftware.com>
wrote:

> For more options, visit this group athttp://groups.google.com/group/wincewebkit?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Rodney Dowdall]

You can debug it using the Microsoft Visual Studio debugger and the Wince
Emulator or a Wince Target. I would try using the "Release with Debug Info"
as wince is somewhat finicky about the sizes of things.

[Alexander Genne]

Hello Rodney,
You're right, the debug build is too large. But trying the "Release
with Debug Info" version the debugger does not break the execution. (I
have deployed the pdb file...)
Then I tried to break using DebugBreak() in code. Now the execution
breaks, but then I get the message that no debug symbols are loaded.
Could You please help me out here?
Thank You in advance
Alex

On Nov 15, 3:32 pm, "Rodney Dowdall" <rdowd...@cranksoftware.com>

> athttp://groups.google.com/group/wincewebkit?hl=en.-Hide quoted text -

>
> > - Show quoted text -
>
> --
> You received this message because you are subscribed to the Google Groups
> "Windows CE WebKit" group.
> To post to this group, send email to wince...@googlegroups.com.
> To unsubscribe from this group, send email to
> wincewebkit...@googlegroups.com.

> For more options, visit this group athttp://groups.google.com/group/wincewebkit?hl=en.- Hide quoted text -

[Rodney Dowdall]

Try turning off all optimizations. The compiler may have optimized where
you put the DebugBreak() so you end up in a system call that does not have
debugging symbols available for it.

Hope this helps,