[XviD-devel] [STATUS] ToDo list for Win32 developers, have a look and send fixes.
Michael Militzer
xvid-devel@xvid.org
Mon, 23 Sep 2002 11:56:23 +0200
Hi,
> >Something went wrong with the project file i commited yesterday. I
> >tested it at work but it seems not to work well now... don't ask me
> >why, but asm files are not processed (so told me sysKin on IRC)
>
> ive fixed the following
> * removed xvidcore.dsw
> * added assembly linkage to libxvidcore.dsp
> * modified vfw.dsp such that it now uses libxvidcore.lib
>
> i have NOT done the libxvidcore.dll stuff; i'd like to hear michaels
> opinion first. anyway the proposed structure is:
> - libxvidcore.dll will export xvid_xxx() functions
> - xvid.dll(vfw) and xvid.ax(dshow) will then dyn-link to libxvidcore.dll
Basically I have no problems with this structure. I'd like to call the core
dll xvidcore.dll because libxvidcore is more unix-style and not that common
for windows. BUT: this is an absolutely low-priority change! The current
xvid.dll has worked nice for a long time and also the win project files have
been worked and tested for a long time, so this combination is stable. I
agree that a xvidcore.dll + xvid.dll + xvid.ax structure is more reasonable
and "better", but it's not a must-have currently. Those changes could be
included into dev-api-3 branch...
> note: sometime ago i was consired merging vfw and dshow together, such
> that they could utilize the same vfw-configuration-dialog code.
> any thoughts on this? (btw, the directshow stuff could be cfg-managed
> to permit compilation without the 100megabyte directx sdk)
sounds good, but is also not high-priority...
bye,
Michael