On Fri, Mar 13, 2009 at 1:20 PM, Ralf Habacker <[email protected]> wrote: > Pau Garcia i Quiles schrieb: > <snip> >> >> That's the point of CMakePorts. >> >> But some projects just say "ok, show me your CMake buildsystem can do >> everything I currently do with autotools/jam/scons/whatever before I >> adopt CMake". And sometimes it's just a matter of timing: maybe >> project X does not want to adopt CMake now but in two months when they >> start having trouble with sonaming with Jam, they'd happily adopt >> CMake. >> >> By having the CMake-ification in CMakePorts, other projects can take >> advantage of a not-yet-official CMake build system for, for instance, >> zlib, lua, libjpeg, etc. >> > not to forget the ones in > http://kde-windows.svn.sourceforge.net/viewvc/kde-windows/trunk/win32libs/
Indeed. I think SaroEngels mentioned them when the discussion about starting CMakePorts started in the CMake mailing list. -- 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
