NOTES for support Libraries


_______________________________________________________________________
for All Developers				     for All Developers



  on Linux
 -========

	o GTK

		A little problem was found on Linux 2.4.29 (Slackware 10.1).
		You may need to create symbolic links to gtk-x.x directory
		in /usr/include:
		
			ln -s /usr/include/gtk-x.x/gtk /usr/include/gtk
			ln -s /usr/include/gtk-x.x/gdk /usr/include/gdk

		this is required by vetWindowGTK.h @ line  '#include <gtk/gtk.h>'

	
	o quicktime4linux

		quicktime4linux2.x gave many errors on Slackware 10.1, but
		quicktime4linux1.4 works fine.


	o ImageMagick
	
		You may download an updated version at http://www.imagemagick.org,
		binaries and self-installing packages are available too.



  on Windows
 -==========

	o xvidcore

		Requires Process Pack (and SP5) for Visual C++ 6.0
		Requires NASM WIN32 exes (on sourceforge.net)

		Currently there's no BCB built project.


	o DirectX

		DirectX is supported by vetDirectXInput and vetDirectXInput2,
		these madules require ./support/directx/amstrmid.lib both, and
		vetDirectXInput2 require also strmbasd.lib and dbghelp.lib.
		amstrmid.lib is available in /Lib folder of DirectX SDK, but
		you need to build strmbasd.lib on your system, Visual Sudio 6.0
		project is /Samples/C++/DirectShow/BaseClasses/baseclasses.dsw.
		dbghelp.lib is available in ./support/directx folder.

		Currently DirectShow base classes are not fully compatible with
		Borland Compilers (invalid OMF record).


	o ImageMagick
	
		ImageMagicK is a big complex library, you may use our compiled
		binaries or build it by yourself, remember that VETLib require
		CORE_DB_magick_.lib.
		You need also to add include directory to MVC enviroment.





_______________________________________________________________________
for Newsbie & Intermediate Developers			    for Newsbie


	o xvidcore

		Compile library may be complex, use binaries .lib or .dll.



  on Linux
 -========

	I suggest to install libraries' packages instead of building 
	by youself, but if you want to try follow Readme files.

	Standard installation process is:

		./configure
		
			This script configures some configuration
			files (as Makefile) to build lib on your system.

		./make
		
			The tool 'make' reads file Makefile and build
			library (hopefully).

		./make install (as root)
			
			The command 'install' starts the real installation
			procedure, usually it just copies static file to
			/usr/lib folder (so you need to be root).







_______________________________________________________________________________________________
Last file update: 17/01/2005    Updated NOTES: http://lnx.ewgate.net/vetlib/distr/support/NOTES