Re: "kde5" or "kf5" ?

On 2013-02-16, Alexander Neundorf wrote: > The tool kde4-config has also been renamed to kde5-config. What's the purpose of this tool in a non-monolithic world? /Sune ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.

Re: "kde5" or "kf5" ?

On Saturday 16 February 2013, Sune Vuorela wrote: > On 2013-02-16, Alexander Neundorf wrote: > > _set_fancy(LIBEXEC_INSTALL_DIR "${LIB_INSTALL_DIR}/kde5/libexec") > > I still don't see a reason for a *shared* libexec directory. libexec is > implementation details of specific libraries, just like

Re: kdelibs frameworks buildsystem under Windows

On Sat, Feb 16, 2013 at 5:48 PM, Alexander Neundorf wrote: > Hi, > > we are doing quite some rework of the build system in the frameworks > branch of > kdelibs. > > Short version: please try to build one of the tier1/ libraries, e.g. > itemmodels/ standalone, and let me know if everything works. >

Re: "kde5" or "kf5" ?

On 2013-02-16, Alexander Neundorf wrote: > _set_fancy(LIBEXEC_INSTALL_DIR "${LIB_INSTALL_DIR}/kde5/libexec") I still don't see a reason for a *shared* libexec directory. libexec is implementation details of specific libraries, just like one shouldn't mess around with each others private's in the

Re: kdelibs frameworks buildsystem under Windows

On Saturday 16 February 2013, Laszlo Papp wrote: > On Sat, Feb 16, 2013 at 5:48 PM, Alexander Neundorf wrote: > > Hi, > > > > we are doing quite some rework of the build system in the frameworks > > branch of > > kdelibs. > > > > Short version: please try to build one of the tier1/ libraries, e.g

Re: "kde5" or "kf5" ?

On Saturday, February 16, 2013 18:41:34 Alexander Neundorf wrote: > > There is no kde5. > > > > > > > > Everything refering to software, pathes and all that should be kf5. It > > does > > not make sense for our libs, neither does it make sense for frameworks. > > > > > > > > (Branding point of vi

Re: Fwd: Re: lib or lib64?

On Saturday 16 February 2013, Valentin Rusu wrote: > On Saturday 16 February 2013 11:50:22 Alexander Neundorf wrote: > > On Saturday 16 February 2013, Valentin Rusu wrote: > > > On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote: > > > > On Friday 15 February 2013, Treeve Jelbert wrote: >

kdelibs frameworks buildsystem under Windows

Hi, we are doing quite some rework of the build system in the frameworks branch of kdelibs. Short version: please try to build one of the tier1/ libraries, e.g. itemmodels/ standalone, and let me know if everything works. Longer version: compiler and build settings are not set anymore in Find

Fwd: Re: lib or lib64?

On Saturday 16 February 2013 11:50:22 Alexander Neundorf wrote: > On Saturday 16 February 2013, Valentin Rusu wrote: > > On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote: > > > On Friday 15 February 2013, Treeve Jelbert wrote: > > > > How can I force everything into one place? > > > >

Re: "kde5" or "kf5" ?

On Saturday 16 February 2013, Sebastian Kügler wrote: > On Saturday, February 16, 2013 10:49:11 Kevin Ottens wrote: > > On Saturday 16 February 2013 10:31:38 Alexander Neundorf wrote: > > > Hi, > > > > > > > > > > > > AFAIK KDE based on KDE frameworks will not be KDE 5, but still KDE4. > > > >

Build failed in Jenkins: kdelibs_frameworks_qt5 #407

See Changes: [scripty] SVN_SILENT made messages (.desktop file) [anantapalani] Hide FindFlex.cmake on Windows so that cmake supplied FindFLEX.cmake is used since FIND_PACKAGE is case insensitive on Windows [anantapalani] Remove unne

Re: "kde5" or "kf5" ?

On Saturday, February 16, 2013 10:49:11 Kevin Ottens wrote: > On Saturday 16 February 2013 10:31:38 Alexander Neundorf wrote: > > Hi, > > > > > > > > AFAIK KDE based on KDE frameworks will not be KDE 5, but still KDE4. > > > > > > > > So... I noticed that we install some things to directories con

Re: QT5_BUILD can go, also from itemmodels ?

Alexander Neundorf wrote: > Hi, > > the cmake variable Qt5_BUILD is still used in a few places, I guess it can > go ? > > Alex Yes, it can go if the code that it covers actually works with Qt 5. If not, I don't see a reason to change it to something else. Thanks, Steve. ___

Re: lib or lib64?

On Saturday 16 February 2013 11:30:13 Valentin Rusu wrote: > On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote: > > On Friday 15 February 2013, Treeve Jelbert wrote: > > > How can I force everything into one place? > > > > If you pull a fresh kdelibs, it should now also go into lib64/. >

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #403

Alexander Neundorf wrote: > On Saturday 16 February 2013, Stephen Kelly wrote: >> KDE CI System wrote: >> > -- Performing Test __KDE_HAVE_FPIE_SUPPORT >> > -- Performing Test __KDE_HAVE_FPIE_SUPPORT - Success >> >> I don't think this option makes sense either. By default, Qt requires >> that PIE

Re: lib or lib64?

On Saturday 16 February 2013, Valentin Rusu wrote: > On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote: > > On Friday 15 February 2013, Treeve Jelbert wrote: > > > How can I force everything into one place? > > > > If you pull a fresh kdelibs, it should now also go into lib64/. > > Let

Re: lib or lib64?

On Sat, 16 Feb 2013 11:30:13 +0100, Valentin Rusu wrote: On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote: On Friday 15 February 2013, Treeve Jelbert wrote: > > > How can I force everything into one place? If you pull a fresh kdelibs, it should now also go into lib64/. Let me know i

Re: lib or lib64?

On Friday 15 February 2013 21:52:31 Alexander Neundorf wrote: > On Friday 15 February 2013, Treeve Jelbert wrote: > > > > > > How can I force everything into one place? > > If you pull a fresh kdelibs, it should now also go into lib64/. > Let me know if it doesn't. Well, I think that other pack

Re: CamelCasing our libraries ?

On Saturday 16 February 2013, Kevin Ottens wrote: > On Friday 15 February 2013 18:15:41 Alexander Neundorf wrote: > > Hi, > > > > any opinions abouut changing our library names to CamelCase, like > > libKCoreAddons.so, together with the package named KCoreAddons ? > > Right now it is libkcoreaddon

Re: "kde5" or "kf5" ?

On Saturday 16 February 2013 10:31:38 Alexander Neundorf wrote: > Hi, > > AFAIK KDE based on KDE frameworks will not be KDE 5, but still KDE4. > > So... I noticed that we install some things to directories containing "kf5", > e.g. > _set_fancy(PLUGIN_INSTALL_DIR"${QT_PLUGIN_INSTALL_DIR}/kf5

Re: CamelCasing our libraries ?

On Friday 15 February 2013 18:15:41 Alexander Neundorf wrote: > Hi, > > any opinions abouut changing our library names to CamelCase, like > libKCoreAddons.so, together with the package named KCoreAddons ? > Right now it is libkcoreaddons, and the cmake variables for it are > kcoreaddons_FOUND, kcor

QT5_BUILD can go, also from itemmodels ?

Hi, the cmake variable Qt5_BUILD is still used in a few places, I guess it can go ? Alex ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

"kde5" or "kf5" ?

Hi, AFAIK KDE based on KDE frameworks will not be KDE 5, but still KDE4. So... I noticed that we install some things to directories containing "kf5", e.g. _set_fancy(PLUGIN_INSTALL_DIR"${QT_PLUGIN_INSTALL_DIR}/kf5") but several other things to "kde5": set(BUNDLE_INSTALL_DIR "/A

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #403

On Saturday 16 February 2013, Stephen Kelly wrote: > KDE CI System wrote: > > -- Performing Test __KDE_HAVE_FPIE_SUPPORT > > -- Performing Test __KDE_HAVE_FPIE_SUPPORT - Success > > I don't think this option makes sense either. By default, Qt requires that > PIE is used, and it sets Qt5_POSITION_I

Re: Finding dependencies in config files

On Saturday 16 February 2013, Stephen Kelly wrote: > commit 6bf0ad9fc7807f341ca924235d2f1e54b8038881 > Author: Alex Neundorf > Date: Sat Feb 9 18:50:06 2013 +0100 > > kguiaddons: check that kconfig has been found in the Config.cmake file > > Alex > > diff --git a/staging/kguiaddons/kg

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #403

Alexander Neundorf wrote: > Hi Stephen, > > On Saturday 16 February 2013, Stephen Kelly wrote: >> KDE CI System wrote: >> > CMake Error at >> > /srv/jenkins/install/linux/x64_64/g++/qt5/kdesupport/extra-cmake- >> >> modules/master/share/ECM-0.0.7/kde-modules/KDECompilerSettings.cmake:404 >> >>

Finding dependencies in config files

commit 6bf0ad9fc7807f341ca924235d2f1e54b8038881 Author: Alex Neundorf Date: Sat Feb 9 18:50:06 2013 +0100 kguiaddons: check that kconfig has been found in the Config.cmake file Alex diff --git a/staging/kguiaddons/kguiaddonsConfig.cmake.in b/staging/kguiaddons/kguiaddonsConfig.c

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #403

Hi Stephen, On Saturday 16 February 2013, Stephen Kelly wrote: > KDE CI System wrote: > > CMake Error at > > /srv/jenkins/install/linux/x64_64/g++/qt5/kdesupport/extra-cmake- > > modules/master/share/ECM-0.0.7/kde-modules/KDECompilerSettings.cmake:404 > > > (message): Qt compiled without support

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #403

KDE CI System wrote: > -- Performing Test __KDE_HAVE_FPIE_SUPPORT > -- Performing Test __KDE_HAVE_FPIE_SUPPORT - Success I don't think this option makes sense either. By default, Qt requires that PIE is used, and it sets Qt5_POSITION_INDEPENDENT_CODE if it does need to be used. CMake already

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #403

KDE CI System wrote: > CMake Error at > /srv/jenkins/install/linux/x64_64/g++/qt5/kdesupport/extra-cmake- modules/master/share/ECM-0.0.7/kde-modules/KDECompilerSettings.cmake:404 > (message): Qt compiled without support for -fvisibility=hidden. This will > break plugins and linking of some applic