please make it easier to hack on frameworks
Kevin Ottens
ervin+bluesystems at kde.org
Sat May 4 19:27:50 UTC 2013
On Saturday 04 May 2013 20:59:32 Alexander Neundorf wrote:
> On Monday 29 April 2013, Aaron J. Seigo wrote:
> > hi ...
> >
> > today i am unable to work on plasma-frameworks. this is because i am
> > currently unable to compile the frameworks branch of kdelibs. in turn,
> > this is because i do not have a recent enough version of cmake.
> >
> > the cmake version required is 2.8.10.20130411. this isn't even a release
> > version of cmake, but a dated snapshot! i am left with the option of
> > moving to cmake from git (something i really would like to avoid) or not
> > working on plasma-frameworks (which is not really an option for me).
> >
> > i am sure there was a good reason to move to this new version of cmake. i
> > am also sure that requiring devel versions of build tools to work on
> > frameworks limits the people who can and will work on it.
> >
> > would it be possible for someone who feels reponsible for frameworks 5 to
> > institute some more developer-friendly requirements here?
>
> I just updated Qt.
> Great that the git updating step is now on
> http://community.kde.org/Frameworks/Building#Qt_5 :-)
>
>
> Now it fails building:
> make[3]: Entering directory
> `/home/alex/src/packages/qt5/build/qtbase/src/corelib'
> /home/alex/src/packages/qt5/build/qtbase/bin/qmake -o Makefile
> /home/alex/src/packages/qt5/qtbase/src/corelib/corelib.pro
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/qt_module.prf:56:
> Cannot find feature qt_module_pris
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/qt_module_headers.
> prf:29: Unexpected return().
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/qt_module.prf:180:
> Cannot find feature qt_common
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/default_post.prf:7
> : Cannot find feature resolve_config
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/create_cmake.prf:1
> 2: Cannot find feature cmake_functions
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/create_cmake.prf:1
> 9: 'cmakeModuleName' is not a recognized replace function.
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/create_cmake.prf:2
> 1: 'cmakeModuleList' is not a recognized replace function.
> /home/alex/src/packages/qt5/build/qtbase/mkspecs/features/qt_functions.prf:1
> 83: resolve_depends(var, prefix) requires one or two arguments.
> /home/alex/src/packages/qt5/build/qtbase/bin/rcc: error while loading shared
> libraries: libQt5Bootstrap.so.5: cannot open shared object file: No such
> file or directory
> make[3]: Leaving directory
> `/home/alex/src/packages/qt5/build/qtbase/src/corelib'
> make[3]: Entering directory
> `/home/alex/src/packages/qt5/build/qtbase/src/corelib'
> /home/alex/src/packages/qt5/build/qtbase/bin/moc -DQT_NO_USING_NAMESPACE -
> DQT_BUILD_CORE_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -
> DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -
> DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -
> DELF_INTERPRETER=\"/lib/ld-linux.so.2\" -DQT_USE_ICU -DPCRE_HAVE_CONFIG_H -
> DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -
> I/home/alex/src/packages/qt5/qtbase/mkspecs/linux-g++ -
> I/home/alex/src/packages/qt5/qtbase/src/corelib -I../../include -
> I../../include/QtCore -I../../include/QtCore/5.1.0 -
> I../../include/QtCore/5.1.0/QtCore -Iglobal -
> I/home/alex/src/packages/qt5/qtbase/src/3rdparty/pcre -
> I/home/alex/src/packages/qt5/qtbase/src/3rdparty/harfbuzz/src -
> I/home/alex/src/packages/qt5/qtbase/src/3rdparty/md5 -
> I/home/alex/src/packages/qt5/qtbase/src/3rdparty/md4 -
> I/home/alex/src/packages/qt5/qtbase/src/3rdparty/sha3 -I.moc/release-shared
> - I. -I/usr/include -I/usr/lib/gcc/i486-slackware-
> linux/4.5.2/../../../../include/c++/4.5.2 -I/usr/lib/gcc/i486-slackware-
> linux/4.5.2/../../../../include/c++/4.5.2/backward -I/usr/lib/gcc/i486-
> slackware-linux/4.5.2/../../../../include/c++/4.5.2/i486-slackware-linux -
> I/usr/lib/gcc/i486-slackware-linux/4.5.2/include -I/usr/lib/gcc/i486-
> slackware-linux/4.5.2/include-fixed -I/usr/lib/qt/include
> -I/usr/local/include
> /home/alex/src/packages/qt5/qtbase/src/corelib/animation/qabstractanimation
> .h -o .moc/release-shared/moc_qabstractanimation.cpp
> /home/alex/src/packages/qt5/build/qtbase/bin/moc: error while loading shared
> libraries: libQt5Bootstrap.so.5: cannot open shared object file: No such
> file or directory
> make[3]: *** [.moc/release-shared/moc_qabstractanimation.cpp] Error 127
> make[3]: Leaving directory
> `/home/alex/src/packages/qt5/build/qtbase/src/corelib'
> make[2]: *** [sub-corelib-make_first] Error 2
>
>
>
> Do I have to run configure again, or is qmake in the meantime able to handle
> this ?
Nope I generally have to run configure again.
> Again with the full list of parameters ?
I do (I in fact have a small script which call configure for me as I often do
the same qt builds). I have no idea if that's mandatory of not.
> If something of that is required, it should be also on that wiki page.
> (I could figure it out, but I'm kind of testing our documentation by just
> following it, so I get the same as probably every other contributor...)
Good idea. Trying to highlight the "first build vs how to track the upstream"
though.
I'm also wondering if we should make kdesrc-build more proeminent as a
solution... I really think it should be the preferred way of working,
simplifies a *lot* of things. Even tested it on one of my former students he
was up and running and moving classes around in no time.
Regards.
--
Kévin Ottens, http://ervin.ipsquad.net
Sponsored by BlueSystems and KDAB to work on KDE Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20130504/a3b5d1d7/attachment.sig>
More information about the Kde-frameworks-devel
mailing list