Re: Windows CE 5.0 bug list

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

What you really want to look at is WINCE500\PUBLIC\COMMON\CESYSGEN\makefile

There, you'll find numerous references to VMINI. This is where you'll find
the logic that turns it into a dll during the sysgen phase.

--
Dean Ramsier - eMVP
Vibren Technologies
http://www.vibren.com/Products/schema_bsp.htm


"Soh Kok Hong" <kokhong.soh@xxxxxxxxx> wrote in message
news:u9fTJqlZFHA.3132@xxxxxxxxxxxxxxxxxxxxxxx
> I've managed to get the vmini.dll built by including the Local Area
Netowork
> option. But I am still not sure exactly how it got built.
>
> I've read the article and I am in the process of tracing through how the
DLL
> got built. I am still reading the cebuild.bat file try to work out how
the
> vmini.dll file got created. Some of the other DLLs like ddi_nop.dll are
> quite easy to figure out because there is a sources file in its source
> directory that indicates that a DLL file should be built. However, the
> corresponding sources file for VMINI says that it should build a library.
> So, VMINI is somewhat special in this respect...
>
> According to your article, in the BSP phase:
>
> " The output of the BSP phase is normally placed in a CPU-specific
directory
> in the platform for EXEs and DLLs on an emulator build. That is,
> C:\WINCE400\PLATFORM\EMULATOR\lib\x86\[retail | debug] for libraries, and
> C:\WINCE400\PLATFORM\EMULATOR\target\x86\[retail | debug] for EXE and DLL
> modules."
>
> In my case, I suppose you can replace EMULATOR with CEPC. However, there
> are also other files generated in this phase (I think) in directories:
>
> %_PROJECTROOT%\cesysgen\oak\lib\x86\[retail | debug] and
> %_PROJECTROOT%\cesysgen\oak\target\x86\[retail | debug]
>
> Is that correct?
>
>
> "Steve Maillet (eMVP)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:uleq0xkZFHA.1368@xxxxxxxxxxxxxxxxxxxxxxx
> > 1) Haven't used that particular machine before so I can't speak about
that
> > one.
> >
> > 2) Did you read the articles I listed? They detail how the system builds
> > it's DLLs in the sysgen phase.
> >
> > --
> > Steve Maillet
> > EmbeddedFusion
> > www.EmbeddedFusion.com
> > smaillet at EmbeddedFusion dot com
> >
> >
>
>


.

Relevant Pages

  • Re: Port Monitor: referencing external libraries in sample code
    ... Be sure that the LIB is actually built before the DLL is built. ... Maxim Shatskih, Windows DDK MVP ... SOURCES file in localmon directory, ...
    (microsoft.public.development.device.drivers)
  • Re: NdisRegisterAdapter
    ... build the libraries that make it up and, build the dll. ... you have to change the SOURCES file to ... project I don't see my dll file but when I compile vmini project vmini.dll ...
    (microsoft.public.windowsce.app.development)
  • Re: S3 Virge driver
    ... Maybe you could try to find out which sources file is responsible for ... line and copying the dll into _FLATRELEASE as a test? ... be for that driver to get built. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Question about PCIbus.dll in Windows CE 6.0
    ... combination in driver DLL 'PCIDriver.dll' ... "Dean Ramsier" wrote: ... So now I have this DLL. ... INCLUDES in the sources file. ...
    (microsoft.public.windowsce.embedded)
  • Re: Question about PCIbus.dll in Windows CE 6.0
    ... Since this is what is in my Template dll entry. ... "Dean Ramsier" wrote: ... TARGETNAME macros to build your dll file. ... INCLUDES in the sources file. ...
    (microsoft.public.windowsce.embedded)