Re: Dependencies for custom driver by Doug
Doug
Wed Nov 29 15:29:38 CST 2006
The RequiredCEModules part is fairly strange, and probably not the best
design.
The catalog has two purposes:
1. Provide a way to control what goes into your image.
2. Provide feedback about what will go into your image.
Step 1 involves letting the user set and unset variables. Step 2 involves PB
analyzing the dependencies and figuring out what features (other than those
requested by the user) will end up in the image. The user only has control
over step 1.
RequiredCEModules affects step 2. It generally means "this catalog component
is wrapped inside some IF statements in a BIB file, and will be included if
both of these other modules are included."
--
// StdDisclaimer.h
// This posting is provided "AS IS" with no warranties, and confers no
rights.
//
"Luke Dunstan" <coder_infidel@hotmail.com> wrote in message
news:1164780095.052642.141670@j44g2000cwa.googlegroups.com...
>
> Bruce Eitman [eMVP] wrote:
>> What do you need the feature group for if there is only one feature of
>> that
>> type? In the editor, sure it needs to show so you can edit it.
>
> Thanks for your reply. OK, I can see your point regarding feature
> groups. Is that related to my other question though? Why can't I delete
> the feature if it requires the "device" module (RequiredCEModules)?
>
> Luke
>
>>
>> --
>> Bruce Eitman (eMVP)
>> Senior Engineer
>> beitman AT applieddata DOT net
>>
>> Applied Data Systems
>> www.applieddata.net
>> An ISO 9001:2000 Registered Company
>> Microsoft WEP Gold-level Member
>>
>> "Luke Dunstan" <coder_infidel@hotmail.com> wrote in message
>> news:1164340018.993304.291650@45g2000cws.googlegroups.com...
>> > Hi,
>> >
>> > I am using Plaform Builder for Windows CE .NET 4.2. I have added some
>> > custom drivers to the .cec file of my BSP (using CEC Editor) in custom
>> > feature groups, but in the catalog they do not behave the same way as
>> > the standard driver types. Firstly, custom drivers using the standard
>> > driver types (e.g. serial drivers) appear in the catalog under:
>> >
>> > Third Party -> BSPs -> My BSP -> Device Drivers -> Serial -> My
>> > Serial Driver
>> >
>> > But the non-standard driver type (feature group) doesn't appear, though
>> > the driver itself does:
>> >
>> > Third Party -> BSPs -> My BSP -> Device Drivers -> My Custom Driver
>> >
>> > I would have expected it to appear in the same way as it looks in CEC
>> > Editor:
>> >
>> > Third Party -> BSPs -> My BSP -> Device Drivers -> My Driver Type ->
>> > My Custom Driver
>> >
>> > Is this normal?
>> >
>> > Secondly, if I set the RequiredCEModules to anything (e.g. just
>> > "device") then I am unable to remove the driver from the platform. If I
>> > try to delete it, Platform Builder just adds it back. My understanding
>> > is that RequiredCEModules specifies what modules the driver depends on,
>> > not what modules depend on the driver, so why would this make the
>> > driver "required"? The standard driver types use RequiredCEModules and
>> > yet I can add or remove them without problems. Is there a way to fix
>> > this?
>> >
>> > Luke
>> >
>