Target designer cant stray from certain component configuration

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I made a test configuration for my device by importing the PMQ file for the
devices (the win32 version of the tool ran, not the dos version).

I made a component out of it and added it to my configuration.
Now when I did a dependency check and build, many MANY MANY components that
I don't need (such as Wireless Zero Configuration, Internet Explorer, Remote
Registry, etc, etc) got added. Any time I try to remove them, it comes back
to me in the dependency check: "System components require this to be added"
or something like that. I can't remove *any* of the ones it added -- they
all "want" to be added back.

Help?

Thanks,
-=matt
 
Matt said:
Hi,

I made a test configuration for my device by importing the PMQ file
for the devices (the win32 version of the tool ran, not the dos
version).

I made a component out of it and added it to my configuration.
Now when I did a dependency check and build, many MANY MANY
components that I don't need (such as Wireless Zero Configuration,
Internet Explorer, Remote Registry, etc, etc) got added. Any time I
try to remove them, it comes back to me in the dependency check:
"System components require this to be added" or something like that.
I can't remove *any* of the ones it added -- they all "want" to be
added back.

Help?

Thanks,
-=matt
Click to expand...

They're going to keep coming back as long as you don't solve the root cause.
Ultimately, something has a dependency which caused components to be added.
You can either use a variety of the dependencies walkers out there or you
can look at the log to see what component caused X to be added. You can
then remove that component and see what component tries to bring that one
back on. Repeat...

It could also be that you are including something from your PMQ which really
isn't needed for your build. When you create a component from your PMQ
file, remember to set it's prototype to "Selector Prototype Component".
That will give it check boxes in the settings pane in Target Designer.
Using those, you can ignore certain components. Remember though, removing a
component doesn't remove it's dependencies. You need to prune early.
 
In addition... you can use CMIEXP.wsf that comes with XPe or a tool like
Component hunter to track down dependency relationships.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
 
Matt said:
Hi,

I made a test configuration for my device by importing the PMQ file for the
devices (the win32 version of the tool ran, not the dos version).

I made a component out of it and added it to my configuration.
Now when I did a dependency check and build, many MANY MANY components that
I don't need (such as Wireless Zero Configuration, Internet Explorer, Remote
Registry, etc, etc) got added. Any time I try to remove them, it comes back
to me in the dependency check: "System components require this to be added"
or something like that. I can't remove *any* of the ones it added -- they
all "want" to be added back.

Help?
Click to expand...
Try junking that and importing the PMQ directly into Target Designer.
Then you can delete the components you don't need.
 
Adora said:
Try junking that and importing the PMQ directly into Target Designer.
Then you can delete the components you don't need.
Click to expand...

ACK!!!

The Selector Prototype Component is your friend. Import the PMQ into CD and
set the prototype. That way in TD you can still avoid the components you
don't need.

my 2 cents...
 
Gordon said:
ACK!!!

The Selector Prototype Component is your friend. Import the PMQ into CD and
set the prototype. That way in TD you can still avoid the components you
don't need.

my 2 cents...
Click to expand...
Well there is that option. :) But if you're only doing one build for one
set of hardware, it strikes me as an unnecessarily complex step.
 
It is up to the developer's style, but the "Selector Prototype" offers the
best flexibility. One can disable components dependencies in the platform
macro component, and these will be unchecked when viewed via Target
Designer.

In this case, he needs all the resource to figure out how to remove the
necessary components and keep the ones he needs.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
 
Sean said:
It is up to the developer's style, but the "Selector Prototype" offers the
best flexibility. One can disable components dependencies in the platform
macro component, and these will be unchecked when viewed via Target
Designer.

In this case, he needs all the resource to figure out how to remove the
necessary components and keep the ones he needs.
Click to expand...
True. I think my opinion on this is somewhat coloured by having a
geriatric dev machine. I tend to avoid changing apps if at all possible. :)
 
Back
Top