Re: CEC Issues

From: Dean Ramsier (ramsiernospam_at_nospam.com)
Date: 11/29/04 

Date: Mon, 29 Nov 2004 09:18:08 -0500

I guess I'm missing something. I don't see the relevancy of
FeatureVariable. Looks to me like it's just another way to set an
environment variable. Whether that variable is a SYSGEN variable or some
other variable (e.g. BSP_xxx) doesn't matter in practice. I'm assuming that
no matter which is used (FeatureVariable or Variable) they both end up
setting the env and end up causing the same result. 

-- 
Dean Ramsier - eMVP
"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> wrote in message
news:%23fOxxHk0EHA.1152@TK2MSFTNGP14.phx.gbl...
> Q1 - Some components in the OS are managed as OptionalChildren.  [...] Is
> there an officially recommended method of adding a
> new driver to the list of OptionalChildren, and if so what is it?  This
> would allow me to provide a driver that would automatically pull in the
> upper level components.
>
> A1: CEC files in V5.0 are no longer responsible for ANY dependency
> information. Catalog items in and of themselves cannot automatically pull
in
> any components. The CEC files can indicate dependencies. That is they
> provide info to the IDE to show the dependency information in the UI, but
> that's it. All dependency information is contained in BAT files called
from
> the workspaces CESYSGEN.BAT. TO get your driver listed as an optional
> child - just re-use the component type guid for the "parent" the simplest
> way to do that is in the CEC Editor. Just uncheck the "CEC File Only"
option
> on the View menu to show the whole catalog. You can then add a child under
> any pre-existing node and it will be added to your CEC file correctly.
>
> Q2 - Same question as '1', but [...]
> A2: Same answer
>
> Q3 - How are we supposed to specify required OS modules?  [...]  The goal
> is to be able to have a driver specify its upper level OS dependencies.
> A3: Required Modules is supported syntactically for backward
compatibility.
> (Although I think that was a mistake) It is completely ignored in V5.0.
ALL
> dependency information for OS modules is provided in BAT files. BY using a
> PBPXML file for the driver project you can use it's ProjSysgen.BAT to
> specify dependency information.
>
> Q4 - What are the best practices on ComponentType guids - should they be
> re-used when it makes sense?  This question is an extension of 1 and 2,
> adding additional options to already provided OS component types.
> A4: See A1 above.
>
> 5 - How is 'Variable' treated differently from 'FeatureVariable'?
> Feature variable is a SYSGEN Variable setting and distinguishes a catalog
> item from a potential driver. Variable is used for any other variables
that
> need setting the most common use for that is MODULE_NAME. The driver
> resolver uses MODULE_NAME to determine which drivers will end up in the OS
> Run-Time Image. The driver resolver uses all of the SYSGEN  variables and
> parses the OS Design BIB files to determine which modules will be included
> into the current configurations Run-Time Image. It then compares that list
> against the catalog looking for catalog items with a matching MODULE_NAME
> value. It then updates the OS Design View tab to show the driver is
> included.
>
> Setting up and using CEC files and how they interoperate with the build
> system is contained in the documentation, although scattered around. It is
> also covered in the new MSDN 2540N training course we wrote for Microsoft.
>
> -- 
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>

Relevant Pages

  • Re: CEC Issues
    ... new driver to the list of OptionalChildren, and if so what is it? ... The CEC files can indicate dependencies. ... All dependency information is contained in BAT files called from ... on the View menu to show the whole catalog. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Question on CEC File ( Need defconfig equalent )??
    ... CEC files must not contain any dependency ... ALL dependency information was moved out into the ... > associated BAT files in V5.0. ... >>> smaillet at EmbeddedFusion dot com ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Question on CEC File ( Need defconfig equalent )??
    ... CEC files must not contain any dependency ... ALL dependency information was moved out into the ... associated BAT files in V5.0. ... >> smaillet at EmbeddedFusion dot com ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Question on CEC File ( Need defconfig equalent )??
    ... CEC files must not contain any dependency ... information to allow compatibility with the command line builds. ... dependency information was moved out into the associated BAT files in V5.0. ... smaillet at EmbeddedFusion dot com ...
    (microsoft.public.windowsce.platbuilder)
Loading