[XviD-devel] patch for dshow inf installer

[Edouard Gomez]

Selon Reini Urban <rurban at x-ray.at>:
> >  - do we have two .inf files (one for dshow and another for vfw)
> >    Pros: users can install two components
> >    Cons: maybe it's harder to decide when to replace the
> >          common xvidcore.dll
>
> Convinced. This is probably the easiest way.
> But I don't really understand the dowsnside of the common xvidcore.dll
> dependency. Either vfw or dshow will update the common file(s). As long
> as the modularization is good enough... Older xvidvwf.dll should work
> with newer xvidcore.dll and the other way round also. Anyone tested this?

It's hard because to know the dll version you have to either trust the ctime
file field (creation time field), or an easy version number retrievable from
the DLL (iirc, it's possible to include this in a dll ressource, but i dunno if
they are intelligent functions in windows that advertise the user he's trying
to replace a version1 lib that is newer than version2)

> Seperate installers (nic or koeppi) can have their own .inf files for
> their setup.exe

A bin builder is responsible for his own .inf files, out of maintree business.
It's packaging business.

--
Edouard Gomez