2009/8/24 Bernhard Reiter <[email protected]>: > Am Samstag, 22. August 2009 15:40:05 schrieb Pau Garcia i Quiles: >> IMHO the best way to achieve this would be converting *all* our 3rd >> party dependencies to CMake. A daunting effort, I know > > Some upstream initiatives habe a very high resistance against using several > build configuration systems, so this task is very hard.
I know :-) There is the CMakePorts ( http://code.google.com/p/cmakeports ) project to temporarily host CMake build systems for projects which won't accept them (yet!) > I wonder about the alternatives. I mean if we could get the game more modular, > we might not need to recompile all libraries by ourselfs. I agree but then we depend on builds provided by other people, which may not be what we need/want. For instance, it's difficult to find MSVC2008 builds for most of the third party dependencies, even more if we talk about 64-bit builds. Then there is the problem of newer versions: you want to move to a new version of OpenSSL and suddenly you need to rebuild every library which depends on libssl, one by one, manually. If we have everything with a CMake build system, building everythins is as simple as creating a "main" CMakeLists.txt with one ADD_SUBDIRECTORY for every third party library we want to build. > Also I think > cross-compilation and thus gcc/mingw is a good option to sidestep some > of the building problems running autoconf/automake on windows. Unfortunately, that's not an option for MSVC. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) _______________________________________________ Kde-windows mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-windows
