Re: Custom Build Command, CEC entry, or BIB file?

From: Chuck Zalinski (charlz_at_online.microsoft.com)
Date: 10/06/04 

Date: Wed, 06 Oct 2004 18:46:04 GMT

Maybe I don't understand #1, but I am assuming it means that the DLL does
not make it to the Flat Release Dir (FRD) (either a copy or link).

I say #1 is a hack because the tools are really designed to get everything
to the FRD. Does #1 even work for makeimg?
For example, when you run the debugger it won't be able to load the debug
files unless they are in the FRD.

No deep dark secrets.
Like you said, just a basic assumption by developers writing the various
tools that your release files will be in the Flat Release Directory.
Not many of the build or debug tools open up the BIB files. Mostly just
makeimg itself.

Relevant Pages

  • Re: [Q] How to speed up build process
    ... files that also get copied to the flat release directory. ... >> won't see the DLL in you Flat Release DIr (FRD) because it wasn't copied ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [Q] How to speed up build process
    ... is setting WINCEREL=1 equivalent to running buildrel after build? ... > won't see the DLL in you Flat Release DIr (FRD) because it wasn't copied ...
    (microsoft.public.windowsce.platbuilder)
  • RE: [Q] How to speed up build process
    ... The batch file "blddemo" does a lot of things to build a final image. ... BSP variables ... won't see the DLL in you Flat Release DIr (FRD) because it wasn't copied ...
    (microsoft.public.windowsce.platbuilder)