Frameworks/Epics/CMake: Difference between revisions

Revision as of 18:39, 4 December 2011

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.

It would be nice if we could get Windows and OSX developers more actively involved with KF5.

Status	Description	Contact
TO DO	We must produce both monolithic and split tarballs for distros.	??	<{{{3}}}>
TO DO	superbuilds	??	<{{{3}}}>
TO DO	Developers are also affected by the splits. Makes building more tedious. Figure out what to do about this	??	<{{{3}}}>
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	develop a future-proof mechanism for providing modules additional to cmake in extra-cmake-modules, i.e. so that using projects can decide which additional stuff they want to use, use some things maybe only for some versions of cmake, etc.	??	<{{{3}}}>
TO DO	come to a decision how to deal with pkg-config under Windows (and OSX ?)	??	<{{{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 1: / Line 1: @@
-This page needs to be refined on the same model than [[Frameworks/Epics/Qt_5.0_Merging]], just adding here important points from Platform 11 not to be missed:
+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.
-* We must produce both monolithic and split tarballs for distros.
-* superbuilds
+It would be nice if we could get Windows and OSX developers more actively
-* Developers are also affected by the splits. Makes building more tedious.
+involved with KF5.
-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.
+{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"
+|- style="background: #ececec; white-space:nowrap;"
+! Status
+! Description
+!  width=120 | Contact
+|-
+{{FeatureTodo|We must produce both monolithic and split tarballs for distros.|??}}
+{{FeatureTodo|superbuilds|??}}
+{{FeatureTodo|Developers are also affected by the splits. Makes building more tedious. Figure out what to do about this|??}}
+{{FeatureTodo|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|??}}
+{{FeatureTodo|develop a future-proof mechanism for providing modules additional to cmake
+in extra-cmake-modules, i.e. so that using projects can decide which
+additional stuff they want to use, use some things maybe only for some
+versions of cmake, etc.|??}}
+{{FeatureTodo|come to a decision how to deal with pkg-config under Windows (and OSX ?)|??}}
+{{FeatureTodo|figure out how to define the default library install dir, taking Debian
+multiarch into account|??}}
+{{FeatureTodo|
+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", |??}}
+{{FeatureTodo|improve the example in kdeexamples/buildsystem/HowToInstallALibrary/, so it
+can serve as reference
+|??}}
+{{FeatureTodo|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
+|??}}
+{{FeatureTodo|
+It would be nice if we could get Windows and OSX developers more actively
+involved with KF5.|Kevin Ottens}}
+|}