What are the plans with CamelCase includes?

[David Faure]

On Friday 27 December 2013 19:01:09 Friedrich W. H. Kossebau wrote:
> So existing code ported from kdelibs would have to explicitely prefix the 
> includes, e.g. be changed like
> #include <KLocalizedString> -> #include <KI18n/KLocalizedString>

Definitely don't want this.

See the QtGui/QLabel -> QtWidgets/QLabel issue between Qt4 and Qt5, we don't 
want to create the same problems with KDE Frameworks.

So yeah, I'm definitely in favour of "*Targets.cmake files,
should include the path including the module prefix"

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5