[Clam-devel] Windows development files distribution

David García Garzón dgarcia at iua.upf.edu
Mon Jan 28 11:18:44 PST 2008


I reviewed  mingw crosscompilation process to assure that all that is working 
at time of release (it wasn't) and to do some changes on the sandbox 
deployment process to simplify it:
http://clam.iua.upf.edu/wikis/clam/index.php/Devel/Windows_MinGW_cross_compile#Status

The old 3rd party library deployment has changed. Instead of:
mingw/pthread/include
mingw/pthread/lib
mingw/pthread/...
mingw/portaudio/lib
...
Now it is like that:
mingw/local/lib
mingw/local/includes
mingw/local/bin

That is, 3rd party libraries are installed with the same prefix, in a posix 
way. This simplifies the configuration and the build system a lot. Now most 
of the libs are compiled using their own build system and i generated a 
tarball with all precompiled third party libraries ready to compile (You 
should install apart Qt, Python, Mingw, SCons...):
http://clam.iua.upf.edu/download/win/svnsnapshots/clam-3rdparty-mingw-20080128.tar.gz
A similar tarball also with compiled clam libraries and headers is available 
here:
http://clam.iua.upf.edu/download/win/svnsnapshots/clam-mingw-1.1.1%7Esvn11119.tar.gz

Not tried in a native windows mingw install but it really works on 
crosscompiling.

Besides that, i managed to crosscompile some future dependencies such as 
libsamplerate, libspeex and libflac. So we have doors wide open in that path.

David.





More information about the clam-devel mailing list