On Fri, Mar 13, 2009 at 12:42 PM, Christian Ehrlicher <[email protected]> wrote:
> It's not just the cmake buildsystem. It's also the ability to actually > compile the sources with msvc or even with > mingw without doing some extra magic (see shared-mime-info for example!) I've looked into emerge/portage/win32libs-sources/shared-mime-info-src/ but I fail to see the magic. What I see is a CMake build system which carefully checks for types, etc., which is good and I have to congratulate you for your nice work (really). Granted, it's not as easy as listing the source files and adding ADD_LIBRARY and TARGET_LINK_LIBRARIES but if that's what's required, that's what's required. > And adding a cmake buildsystem just because it would be nicer instead using > the working one is a waste of time > for kde-windows. I agree with that but sometimes it's too inconvenient or plain impossible to build with MSVC with what upstream provides. In those cases, CMake-ifying that project makes MSVC possible and easy. For instance, I recently CMake-ified some third-party projects for work just because they were a pain to build on Windows (they used scons, bjam and one of them even a custom shell script). For one of those projects (luabind), upstream asked me to add the tests to the build system, then he'll gladly accept the CMake buildsystem. The reason? He's been having trouble with sonaming with bjam. -- 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
