"Mike McCormack" mike@codeweavers.com wrote:
ChangeLog: Tim Ferguson Tim.Ferguson@infotech.monash.edu.au Mike McCormack mike@codeweavers.com
- Port Tim Ferguson's ICCVID codec to Wine
Mike, could you put the iccvid sources at the same place as msrle32 (dlls/msvideo) and resend the patch?
Hi Dmitry,
I asked Alexandre where it should go, and he said wine/dlls was an appropriate place. I don't mind either way...
Mike
Dmitry Timoshkov wrote:
Mike, could you put the iccvid sources at the same place as msrle32 (dlls/msvideo) and resend the patch?
"Mike McCormack" mike@codeweavers.com wrote:
I asked Alexandre where it should go, and he said wine/dlls was an appropriate place. I don't mind either way...
I don't mind either, but if the new iccvid code will be placed under dlls/ then dlls/msvideo/msrle32 should be moved there as well.
On January 14, 2004 01:05 am, Dmitry Timoshkov wrote:
I don't mind either, but if the new iccvid code will be placed under dlls/ then dlls/msvideo/msrle32 should be moved there as well.
I'd much rather move msrle32 to dlls/, then create new DLLs deep inside the dir hierarchy. Ideally we should have all DLLs just under dlls/, let's not make the problem worse.
Dimitrie O. Paun a e'crit :
On January 14, 2004 01:05 am, Dmitry Timoshkov wrote:
I don't mind either, but if the new iccvid code will be placed under dlls/ then dlls/msvideo/msrle32 should be moved there as well.
I'd much rather move msrle32 to dlls/, then create new DLLs deep inside the dir hierarchy. Ideally we should have all DLLs just under dlls/, let's not make the problem worse.
I still don't see the point of having a unique dlls/ flat structure. Which more than 100 dlls right now, I do think we need to structure it. So putting the video codec in msvideo directory seems the easiest structure. We could also envisage to have a drivers or codecs directory, but that'll boil down to the same thing. A+
-
Dimitrie O. Paun -
Dmitry Timoshkov -
Eric Pouech -
Mike McCormack