Re: Help Adding Apps to CE 6.0 OS Design

Thanks a lot for the replies. At this point, I'd like to build the app as
standalone, i.e just include it in the project.bib and see if it works or
not. Later on, I like to be able to make my app be a part of subproject of
the OS design - so that I can then debug not only the app, but system
level
calls as well.

I don't see what one has to do with the other. You can do application debug
with the kernel debugger, although I don't find that very useful, or just
debug the OS pieces with the Platform Builder run of VS2005 and debug the
application with VS2005's ordinary application debugger.

Now, I understood how to add my app to project.bib and build the image.
Since the application I am building is an exe, supported by many .libs
and
.dlls, do I need to add the libs and dlls used by my app to the MODULES
(or
FILES ?) section of project.bib as well?
For ex: my exe is located C:\MyApp\....\Soln\Debug\app.exe and all the
libraries/dlls it consumes are in under their own directory, which is
somewhere buried inside C:\MyApp\ProjA...\ , C:\MyApp\ProjB...\ ,...etc

Well, what you do with LIBs, since they are not executable directly, isn't
relevant. DLLs that the application uses will presumably either a) have to
be in the OS via the BIB file or b) copied to the device in some way before
the application uses them. How you want to do that is pretty flexible. I'd
be inclined to include them in the OS via the BIB file if the EXE is
included in the BIB file but it's not required or something.

My feeling is that you really need to go to a training on Windows CE 6.
After that, I think that you'd have a pretty good idea of how the kernel
debugger works, how to add files to the OS, hwo to debug things in the OS,
both applications and DLLs, as well as the components of the OS itself.

Paul T.


.

Relevant Pages

  • Re: Deployed app causes mfc71d.dll error
    ... > dlls. ... When I start the app, it bombs with an error about a missing ... So somehow my release build app is dependent on the debug ... Link with /verbose and /test on the linker command line and search the ...
    (microsoft.public.vc.language)
  • Re: windbg & vs 2005 - cant use debugging symbols on vs2005 dlls!
    ... The problem is when we migrated our dlls to ... suddenly their symbols would not load anymore (and they also appear ... > to crash, even though they compile fine, which is why I tried to debug). ... Likewise, when I debug the dlls solution with the app, the app will ...
    (microsoft.public.vc.debugger)
  • Re: Deployed app causes mfc71d.dll error
    ... When I start the app, it bombs with an error about a missing ... So somehow my release build app is dependent on the debug ... Make sure the EXE and all seven DLLs are built with release build. ... files on the deployment machine. ...
    (microsoft.public.vc.language)
  • slow debug
    ... i've developing an app with vs2005 for CompactFramework, with all Service Packs, when i try to debug the application over the machine, the VS2005 copy all dlls and programto the machine, ex: System, System.XML, System.Windows.Form, etc. Altought in the machine, these file already ... i've been searching for debug app without copy all these dlls, but i couldn't find it, how i can debug app, with only pass to the machine the program?, the proccess take about 4 min in execute the program, because before copy all these things. ...
    (microsoft.public.dotnet.framework.compactframework)
  • CreateProcess DEBUG_PROCESS fails to show any window
    ... it creates the proc with a valid thread and proc handle ... returned showing fine in Task Man but the window fails to load. ... IF I create an appication without debugging info and the target app to ... load has no debug info CreateProcess with DEBUG flag loads the process ...
    (microsoft.public.vc.debugger)
Loading