RawDep resource

  • Thread starter Thread starter =?iso-8859-1?Q?G=F6ran_Davidsson?=
  • Start date Start date
?

=?iso-8859-1?Q?G=F6ran_Davidsson?=

Hello,

When I look in a component shipped with XPe (for example
accessibility core) I can see a resource labeled RawDep
that points to a individual file.

How can I create similar resources in my components?

/Göran
 
Raw Dependencies are only used when "compiling" the SLDs during our build
process before the product is released. There is no need for Raw Deps in
your usage, you can use Component Dependencies to express dependencies.

We convert the Raw Deps to Component Dependencies in our build process right
before shipping the product, so there is no use for that resource after we
ship the product <grin>

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


Hello,

When I look in a component shipped with XPe (for example
accessibility core) I can see a resource labeled RawDep
that points to a individual file.

How can I create similar resources in my components?

/Göran
 
How should I handle the situation that my component
requires the file msdv.inf. When I search the database for
the file I found many components that include that file,
but I don't want to include a display adapter for instance
just to get the file included.

What I have done now is created a copy of the file in the
repository of my component. It works fine, but if the file
is updated I get som problems.

Should I create a component just for that file, similar to
the primitive components, and use the existing repository
(default XPe) for that component? Is that a better way?

Thanks
/Göran
 
It's just an inf, it has no dependencies, so you can simply add it as a file
resource to your component.

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


How should I handle the situation that my component
requires the file msdv.inf. When I search the database for
the file I found many components that include that file,
but I don't want to include a display adapter for instance
just to get the file included.

What I have done now is created a copy of the file in the
repository of my component. It works fine, but if the file
is updated I get som problems.

Should I create a component just for that file, similar to
the primitive components, and use the existing repository
(default XPe) for that component? Is that a better way?

Thanks
/Göran
 
Andy is correct,

But in your case are you sure that inf file is only thing you need?

It is inf file and it does not have dependencies so if you only need to have
this file in your build you can add it as file resource.

But are you sure that you need only file.
It seams to me that this is driver and that it also registers many filters.
If you need DV functionality I'm afraid that you will have to use one of the
components you saw, or make your own based on one of them.


Regards,
Slobodan

How should I handle the situation that my component
requires the file msdv.inf. When I search the database for
the file I found many components that include that file,
but I don't want to include a display adapter for instance
just to get the file included.

What I have done now is created a copy of the file in the
repository of my component. It works fine, but if the file
is updated I get som problems.

Should I create a component just for that file, similar to
the primitive components, and use the existing repository
(default XPe) for that component? Is that a better way?

Thanks
/Göran
 
No, the inf file is not the only thing I need. Let me
explain in more detail what I want to do.

I want to create a component for the display adapter ATI
Radeon Mobility 7500. And in the inf file for the device
driver there is several include=msdev.inf statements. So I
use a lot more files, but I guess that one must be present
as well.

But my question was if I should copy the file from the XPe
original repository to my own repository for the ATI
component, or how should I add the file resource
(msdv.inf). I mean, the msdv.inf file is an original WinXP
file, but it is not present as an own component. Do you
understand my question?

If I look at the ATI RADEON Mobility (HP) component in TD,
I can see that in the inf file for the driver
(atiradn1.inf) MS has just commented the include=msdv.inf
statements out. Simple, but can I do the same. I have no
idea!!

Thank you
/Göran
 
I think that you can only copy this file, since it is not required by video
driver to function properly.
It seams that someone from ATI used too much copy/paste option and they have
used this include in every section, even where it is not needed. They
commented other DV related things but not the include itself.
You can remove it from section regarding your card model in ATI inf file. Or
add file to your repository. It should work.

Regards,
Slobodan



No, the inf file is not the only thing I need. Let me
explain in more detail what I want to do.

I want to create a component for the display adapter ATI
Radeon Mobility 7500. And in the inf file for the device
driver there is several include=msdev.inf statements. So I
use a lot more files, but I guess that one must be present
as well.

But my question was if I should copy the file from the XPe
original repository to my own repository for the ATI
component, or how should I add the file resource
(msdv.inf). I mean, the msdv.inf file is an original WinXP
file, but it is not present as an own component. Do you
understand my question?

If I look at the ATI RADEON Mobility (HP) component in TD,
I can see that in the inf file for the driver
(atiradn1.inf) MS has just commented the include=msdv.inf
statements out. Simple, but can I do the same. I have no
idea!!

Thank you
/Göran
 
Göran Davidsson said:
No, the inf file is not the only thing I need. Let me
explain in more detail what I want to do.

I want to create a component for the display adapter ATI
Radeon Mobility 7500.


There is already a ATI Radeon component in the Component Database that
should perfectly function rather than making the component if thats
what ur looking for!





And in the inf file for the device
 
Back
Top