[vtk-developers] vtk cvs and vfw.dll

Luca Picello luca.picello at libero.it
Wed Aug 17 14:21:35 EDT 2005


in my vtkIO.dll the dependency required is exactly VFW32.DLL.
I do use Borland C++ Builder 6, it includes all files needed to link to 
vfw32.ddl
(vfw32.lib, vfw.h, vfwmsgs.h, vfw32.def).
is it possible you have something which links (visual studio?) to 
AVIFIL32.dll ?
AVIFIL32.dll is present in my system too.

luca



Amy Squillacote wrote:

> From poking around on the web, it looks like vfw32.lib points to 
> MSVFW32.dll, AVIFIL32.dll, and AVICAP32.dll (all three of which exist 
> on my system); it also looks like vfw32.dll does not exist.
>
> - Amy
>
> At 01:46 PM 8/17/2005, David Cole wrote:
>
>> Actually, there is no *vfw32.dll* on my system either. Yet it works 
>> for me. I do have AVIFIL32.dll and using depends.exe, I see that this 
>> is the correct dependency added to vtkIO.dll by the addition of the 
>> vtkAVIWriter.
>>
>> Luca, can you use "depends.exe" and post the list of dependent dll's 
>> of vtkIO here. Apparently, vfw32.lib pulls in dependencies to DLL's 
>> with *other* names. There must be something else going on here...
>>
>>
>> Luca Picello wrote:
>>
>>> my OS is WindowsXP pro and no VFW32.DLL is present in my system...
>>> does it come from the omnipresent visual studio? ;-)
>>>
>>> ciao
>>>
>>>
>>> Sebastien BARRE wrote:
>>>
>>>> At 8/17/2005 07:09 PM, Luca Picello wrote:
>>>>
>>>>> Well... I believe we should, for example when starting vtk.exe 
>>>>> (for TCL) it halts with the red-messagebox-of-death complaining 
>>>>> for VFW32.DLL. and the application terminates.
>>>>
>>>>
>>>>
>>>>
>>>> What is your OS ?
>>>>
>>>> We can definitely put the new vtkAVIWriter class inside the 
>>>> VTK_USE_VIDEO_FOR_WINDOWS conditional, but it's a neat class that 
>>>> was requested in the past on the mailing list, and the default for 
>>>> that var is OFF. Maybe we should have CMake detect if the DLL is 
>>>> preset and set VTK_USE_VIDEO_FOR_WINDOWS accordingly, instead on 
>>>> relying on the user to figure it out. I'm actually surprised that 
>>>> DLL is not on the system by default...
>>>>
>>>>
>>>> .
>>>
>>>
>>>
>>
>> _______________________________________________
>> vtk-developers mailing list
>> vtk-developers at vtk.org
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
> .
>




More information about the vtk-developers mailing list