Revision as of 22:09, 6 December 2011

CMake Required Features and Migration Epic

Forewords

Roughly this epic is about CMake upstream contributions we need done, getting stuff into the extra-cmake-modules (e-c-m) project and the tooling around that to allow our developers to build the whole lot.

Definition of Done

for stuff which is upstreamed into cmake: merged into the master branch
every source incompatible change must be noted here: http://techbase.kde.org/Development/ECM_SourceIncompatChanges
kde-frameworks-devel has been warned about CMake API changes introduced by the feature

Backlog

Status	Description	Contact
DONE	Upstream automoc into cmake. Done since 2.8.6.	Alex Neundorf
DONE	Extend FeatureSummary.cmake to make MacroLogFeature.cmake unnecessary. Done since 2.8.6.	Alex Neundorf
DONE	Merge MacroOptionalFindPackage.cmake in CMake. find_apckage() has been extended with 2.8.6 so that this is not necessary anymore.	Alex Neundorf
DONE	Create project extra-cmake-modules for distributing additional Find-modules	Alex Neundorf
DONE	Sync our Find-modules from kdelibs/cmake/modules/ with the ones in CMake. Done with CMake 2.8.7	Alex Neundorf
DONE	Merge our export-header stuff into cmake. Done with CMake 2.8.6	Stephen Kelly
IN PROGRESS	Merge or make unnecessary a whole bunch of macros from kdelibs/cmake/modules/. Mostly done. Details see KDE_Core/Platform_11/Buildsystem/FindFilesSurvey	Alex Neundorf, Stephen Kelly
IN PROGRESS	Design and implement mechanism to make extra-cmake-modules flexible usable, also for non-KDE-projects.	Alex Neundorf
IN PROGRESS	Make superbuilds robust and usable. This will make building all the small git repositories easier. See https://projects.kde.org/projects/kde/superbuild	Alex Neundorf
IN PROGRESS	Come to a decision how to deal with pkg-config under Windows (and OSX ?). Input needed, especially from Windows and OSX developers.	Alex Neundorf
TO DO	Review the Find-modules in kdelibs (over 100), and find out which ones are currently needed in the frameworks branch. Here is an overview over the current state: http://community.kde.org/KDE_Core/Platform_11/Buildsystem/FindFilesSurvey	??	<{{{3}}}>
TO DO	Figure out how to define the default library install dir, taking Debian multiarch into account	??	<{{{3}}}>
TO DO	Figure out how to deal with the install dirs in general: use GNUInstallDirs.cmake coming with cmake ? keep the support for "if I install to the same prefix as kdelibs (...what is kdelibs then ?), I want the same set of install dir",	??	<{{{3}}}>
TO DO	improve the example in kdeexamples/buildsystem/HowToInstallALibrary/, so it can serve as reference	??	<{{{3}}}>
TO DO	somebody has to do the actual porting. Back in the KDE3->KDE4 days Laurent Montel did most of this work. Here is a (hopefully) complete list of changes: http://techbase.kde.org/Development/ECM_SourceIncompatChanges	??	<{{{3}}}>
TO DO	It would be nice if we could get Windows and OSX developers more actively involved with KF5.	Kevin Ottens	<{{{3}}}>

@@ Line 2: / Line 2: @@
 == Forewords ==
-Roughly this epic is about CMake upstream contributions we need done, and the tooling around that to allow our developers to build the whole lot with a single command '''and''' to produce different granularity of tarballs for our downstreams.
+Roughly this epic is about CMake upstream contributions we need done, getting stuff into the extra-cmake-modules (e-c-m) project and the tooling around that to allow our developers to build the whole lot.
 == Definition of Done ==
 * for stuff which is upstreamed into cmake: merged into the master branch
+* every source incompatible change must be noted here: http://techbase.kde.org/Development/ECM_SourceIncompatChanges
 * kde-frameworks-devel has been warned about CMake API changes introduced by the feature