[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re : Re: starting to split the multimedia DLLs
From:       eric.pouech () lemel ! fr (eric pouech)
Date:       1999-08-27 7:08:28
[Download RAW message or body]

well, my first proposal was to put the drv in subdirectories of the mmsystem
/winmm dll tree (since they are drivers only used by those DLLs), but it 
doesn't reach a consensus (there were in fact two sub dirs in the mmsystem/
winmm dir, one holding all the mci drivers, another one for the low level 
drivers.
basically, there are three alternatives:
- flat one under wine/dlls/ (the one below)
- wine/dlls/winmm with two subdirs dlls/winmm/mcidrv (with one subdir for 
each mci driver) and dlls/winmm/lldrv (with one subdir for each low level 
driver: OSS, wave mapper, midi mapper...)
- wine/dlls/winmm with one subdir dlls/winmm/drv (with one subdir for each 
mci and low level driver)
- wine/drvs as proposed by Bertho. Anyway, a .drv is a DLL (from a technical
 point of view), but also expose some specific APIs. Could be also done. One
 advantage of this method is that this could ease the handling in the build 
process (if something specific is needed for drivers on top of DLLs)

technically, the four alternative are equivalent. from an organization point
 of view the second and third stress the link between components of the 
multimedia sub system. The fourth stresses the point that some of those 
components are drivers.
(anyway, I don't like much the dlls/ dir growing and growing with its 
current flat structure, so i'd favor the second or third one. The fourth one
 could also be an alternative. I don't have anything against it)

>Eric Pouech wrote:
>[snip]
>> Alexandre, since it's likely the MM files will be heavily
>> reorganized, I'd like to get your agreement on the way to handle
>> it (and if you agree to do it), and the best steps to go for it
>> (both on your side and my side). As already discussed on wine-devel,
>> the current multimedia directory shall disapear and be replaced by
>> a list of new ones under dlls:
>> dlls/winmm/     WINMM + MMSYSTEM
>> dlls/mciavi/    MCIAVI.DRV
>> dlls/mciwave/   MCIWAVE.DRV
>> dlls/mcicda/    MCICDA.DRV
>> dlls/mcimidi/   MCIMIDI.DRV
>> dlls/mcianim/   MCIANIM.DRV
>> dlls/wavemap/   MSACM.DRV (no existing files yet)
>> dlls/midimap/   MIDIMAP.DRV (no existing files yet)
>> dlls/wine_oss/  WINE_OSS.DRV (maybe other name ...)
>> dlls/wine_ljoy/ WINE_LJOY.DRV (maybe other name ...)
>> dlls/dsound/    DSOUND
>> dlls/dplay/     DPLAY + DPLAYX
>
>[snip]
>
>Wouldn't it be better to put the *.drv stuff in a new directory
>"drvs/..." than under dlls? I guess that it would be more appropriate
>because they are not truly dlls but real drivers.
>
>Greetings Bertho
>
>
>


=========================================================================

[prev in list] [next in list] [prev in thread] [next in thread]