Using qplatformdefs.h

2012-11-25 Thread David Faure
KF5-with-Qt5 compilation is currently broken because we can't locate qplatformdefs.h This used to come from this line: tier1/kcoreaddons/src/CMakeLists.txt: 74: include_directories(${QT_MKSPECS_DIR}/default) # for qplatformdefs.h But QT_MKSPECS_DIR isn't set anymore. How can we get this back?

Re: kcoreaddons: which optional features should be know to users ?

2012-11-25 Thread David Faure
On Sunday 25 November 2012 12:40:01 Alexander Neundorf wrote: > Hi, > > the kcoreaddons library in kdelibs/tier1/ has a bunch of configure checks, > for FAM, inotify and some more. > > If a developer who uses kcoreaddons might need to know whether those > features have been built into kcoreaddons

Re: KLocale plans

2012-11-25 Thread Chusslove Illich
> [: David Faure :] > I think this should be QLibrary("kf5/ktranscript"), and ensuring the file > on disk is called ktranscript.so (no "lib" in front). I forgot to say I tried that too :) Here's the sequence: $ grep 'QLib.*ktranscript' $SRCDIR/kdecore/localization/klocalizedstring.cpp QLi

Re: KLocale plans

2012-11-25 Thread David Faure
On Sunday 25 November 2012 00:59:59 Chusslove Illich wrote: > > [: David Faure :] > > Porting from KLibrary to QLibrary really brings up only one question, how > > to locate ktranscript.so. But since the idea is that QT_PLUGIN_PATH must > > be set to the KF5 install prefix + /lib/plugins, it might

kcoreaddons: which optional features should be know to users ?

2012-11-25 Thread Alexander Neundorf
Hi, the kcoreaddons library in kdelibs/tier1/ has a bunch of configure checks, for FAM, inotify and some more. If a developer who uses kcoreaddons might need to know whether those features have been built into kcoreaddons or not, this information should be configured into kcoreaddonsConfig.cma