Re: Forwarding headers: current status
On Thursday 02 January 2014 12:14:19 David Faure wrote:
TODO: get agreement on include/KF5/FrameworkName/{everything_here} and
convert all repos.
Done!
Make sure to update everything (ECM, all frameworks, plasma...) otherwise
you'll get compile errors. This is a good time to build from scratch, too,
i.e. removing both builddir and installdir, to avoid old headers left over in
wrong places.
So, fixing ThreadWeaver on Saturday and tagging on Sunday.
Meanwhile maybe someone can test the result of the packaging scripts,
preferrably on a machine without a KF5 development setup?
http://www.davidfaure.fr/2013/extra-cmake-modules-4.95.0.tar.xz
http://www.davidfaure.fr/2013/karchive-4.95.0.tar.xz
Warning to the slashdot crowd: these are not the actual TP1 tarballs :)
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Forwarding headers: current status
On Thursday 02 January 2014 00:58:21 David Faure wrote:
karchive -- TODO split out KArchiveFile etc. I'll do that next.
Done.
kded [why does it install a kded_version.h?]
Fixed.
kjsembed [why does it install a kjsembed_version.h and a kjsembed_export.h,
if it has no headers?]
Fixed.
TODO: threadweaver -- pending reply from Mirko.
Forwarded my answer, forgot to CC him.
TODO: move _version.h headers to include/lowercase_framework. I see no
reason why they should stay at the toplevel...
Hmm, one reason is that there's one per framework, not one per lib.
E.g. kio_version.h and KIOCore, KIOWidgets, KIOFileWidgets subdirs.
Maybe I save myself some work by leaving _version.h headers at the toplevel ;)
TODO: get agreement on include/KF5/FrameworkName/{everything_here} and convert
all repos.
Then we can release :)
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Forwarding headers: current status
After a whole day of converting frameworks, here's the current status: DONE: kitemviews kconfig kglobalaccel kcoreaddons kauth kcodecs karchive -- TODO split out KArchiveFile etc. I'll do that next. kguiaddons ki18n kwidgetsaddons kconfigwidgets kiconthemes kcompletion kwindowsystem kcrash kdbusaddons kservice ktextwidgets kxmlgui kitemmodels kdnssd-framework (namespaced) kplotting solid (namespaced) kjobwidgets kbookmarks knotifications kwallet-framework kunitconversion (namespaced) kparts (namespaced) kdewebkit kpty kmediaplayer (namespaced) kemoticons kdesu (namespaced) kdeclarative (namespaced) kcmutils frameworkintegration kidletime knewstuff kprintutils kio (partly namespaced) knotifyconfig kross (namespaced but still in a subdir) khtml (only 3 headers, not all the dom headers) SKIPPED because they don't install headers: kdoctools kdesignerplugin kimageformats kf5umbrella kinit kfileaudiopreview kded [why does it install a kded_version.h?] kjsembed [why does it install a kjsembed_version.h and a kjsembed_export.h, if it has no headers?] SKIPPED for other reasons: kde4support (already has them, in the KDE subdir) attica, strigi, kde-kactivities (not frameworks yet, see my question on k-c-d) kjs -- a bit of a mess in terms of public headers, never had forwarding headers anyway TODO: threadweaver -- pending reply from Mirko. TODO: move _version.h headers to include/lowercase_framework. I see no reason why they should stay at the toplevel... -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
