I appreciate the feedback. As they say, two heads are better than one.

Looking at this hint in the first error log:

Code: Select all

CMake Error at CMakeLists.txt:62 (find_package):
Could not find a package configuration file provided by "Phonon4Qt5"
(requested version 4.6.60) with any of the following names:

Phonon4Qt5Config.cmake
phonon4qt5-config.cmake

Add the installation prefix of "Phonon4Qt5" to CMAKE_PREFIX_PATH or set
"Phonon4Qt5_DIR" to a directory containing one of the above files. If
"Phonon4Qt5" provides a separate development package or SDK, be sure it has
been installed.

I found that `Phonon4Qt5Config.cmake` does exist in the phonon build directory `/opt/kde/build/phonon/`. The log (as above) says "requested version 4.6.60", so I opened the file to see if the version matched and it doesn't. Source below:

Code: Select all

# config file for phonon library

# known at buildtime
set(PHONON_VERSION "4.8.51")

get_filename_component(currentDir ${CMAKE_CURRENT_LIST_FILE} PATH) # get the directory where I myself am
get_filename_component(rootDir ${currentDir}/../../../ ABSOLUTE) # get the chosen install prefix


set(PHONON_NO_GRAPHICSVIEW true)
set(PHONON_PULSESUPPORT TRUE)
set(PHONON_FIND_EXPERIMENTAL ON)
set(PHONON_QT_COMPAT_HEADERS OFF)

# install locations
set(PHONON_INCLUDE_DIR "${rootDir}/include/phonon4qt5")

set(PHONON_LIBRARY_DIR "${rootDir}/lib64")
set(PHONON_BUILDSYSTEM_DIR "/opt/kde/install/share/phonon4qt5/buildsystem/")
set(PHONON_LIB_SONAME "phonon4qt5")

if(NOT TARGET Phonon::phonon4qt5)
  include(${currentDir}/PhononTargets.cmake)
endif()

set(PHONON_LIBRARY Phonon::phonon4qt5)

# Find Experimental.

# Iff it was specified as component we require it.
# Else if we built with it we try to find it quietly.
# The latter part is to provide backwards compatibility as a simple finding of
# Phonon would also drag in experimental. To simulate this we'll look for it
# silenetly while not failing if it was not found. Ultimately it was the
# config consumer's responsibility to check if experimental was actually found.
# So nothing changes there. Config consumers can however now use it as a
# component to force an error when it isn't available.
if("${Phonon4Qt5_FIND_COMPONENTS}" MATCHES ".*(Experimental|experimental).*")
    find_package(Phonon4Qt5Experimental ${PHONON_VERSION} EXACT CONFIG REQUIRED
                 PATHS ${currentDir}
                 NO_DEFAULT_PATH)
elseif(PHONON_FIND_EXPERIMENTAL)
    find_package(Phonon4Qt5Experimental ${PHONON_VERSION} EXACT CONFIG QUIET
                 PATHS ${currentDir}
                 NO_DEFAULT_PATH)
endif()

# Convenience.
set(PHONON_LIBRARIES ${PHONON_LIBRARY} ${PHONON_EXPERIMENTAL_LIBRARY})
# The following one is only for compatiblity
set(PHONON_LIBS ${PHONON_LIBRARIES})
set(PHONON_INCLUDES ${PHONON_INCLUDE_DIR} ${PHONON_INCLUDE_DIR}/KDE)
if (PHONON_QT_COMPAT_HEADERS)
    list(APPEND PHONON_INCLUDES ${PHONON_INCLUDE_DIR}/Phonon)
endif()

# Find Internal is included in the backends' finders rather than here.
# http://lists.kde.org/?l=kde-multimedia&m=135934335320148&w=2


I don't know if this is the cause of the build failure, but as you can see, requested phonon version 4.6.60 doesn't match the version specified in the Phonon4Qt5Config.cmake file.

have you followed https://community.kde.org/Guidelines_an ... rom_source ?

suggest you contact progdan http://www.dvratil.cz/ as it appears he would be the one most familiar with doing this on Fedora and as he has 5.6 in beta form you could just add the noted repos from his posting "PLASMA 5.6 BETA AVAILABLE ON FEDORA"

Yes, I have been using those guidelines.

Cheers for the referral, perhaps progdan will point me in the right direction.

It turned out to be a multiarch issue of sorts. yum-builddeps was showing all dependencies as met when they actually weren't. I had pulseaudio-libs-devel.i686 but was missing pulseaudio-libs-devel.x86_64.

Now frameworks have built smoothly right up to 'frameworkintegration', and I'm now better equipped to debug other such cross-compilation errors. Should be easy... (fingers crossed)

Hi there -

I just registered to say thanks! On centos7 with epel-testing enabled I can build 99% of git master branch using kdesrc-build, and plasma runs great on centos7!

I needed (from epel-testing) Cmake. It's a bit unintuitive, but the maintainer has chosen to rename it to cmake3, so you need to alias all calls to 'cmake' > cmake3. Perhaps kde will support this later.

also installed qt-5.6 (not required - qt5.5 is already in epel)

Somewhat painfully I needed wayland1.7+. I found it from a copr by jmliger (gnome3.16 backports). mesa-libwayland included)

basically* from there 120 of 121 packages in the kf5-frameworks and kf5-workspace build and run.

Hey Aloysius, that's great news, grats!

I've been making progress, albeit slow as I've haven't had much time to dedicate. All frameworks compile successfully but I haven't gotten all the workspace modules working yet.

I'm 112/121 built atm.

progdan wrote:... First I need to import Frameworks into EPEL, but that is currently blocked on some missing dependencies, so I need to solve that first. Sorry it's all taking so long.

I can now happily report that KF5 builds are now on their way to EPEL-7 testing repositories:

KF5 : https://bodhi.fedoraproject.org/updates ... f057025262

and some prerequisite dependencies:

phonon-qt5 : https://bodhi.fedoraproject.org/updates ... 8e9b956ff2
dbusmenu-qt5 : https://bodhi.fedoraproject.org/updates ... c6830d3eb1
polkit-qt5-1 : https://bodhi.fedoraproject.org/updates ... 83b0af5ec7

rdieter wrote:

progdan wrote:... First I need to import Frameworks into EPEL, but that is currently blocked on some missing dependencies, so I need to solve that first. Sorry it's all taking so long.

I can now happily report that KF5 builds are now on their way to EPEL-7 testing repositories:

KF5 : https://bodhi.fedoraproject.org/updates ... f057025262

and some prerequisite dependencies:

phonon-qt5 : https://bodhi.fedoraproject.org/updates ... 8e9b956ff2
dbusmenu-qt5 : https://bodhi.fedoraproject.org/updates ... c6830d3eb1
polkit-qt5-1 : https://bodhi.fedoraproject.org/updates ... 83b0af5ec7

I'm not entirely sure what this means, but it sounds like excellent news! I have built everything I need from 'kf5-workspace' and 'kf5-frameworks' except for the plasma-desktop itself, which at present escapes me. I guess I should wait.

Finally built successfully!

so - have you been able to build plasma against the epel-testing packages?

I've tried with kdesrc-build running include kf5-workspace-build-include which builds plasma workspace,etc which seems to build but...

I've set my kde (KF5) dir to /usr/ so it installs along side the repo-provided frameworks, however trying to log in to the installed gdm "plasma" option I simply get a black screen of death with no warnings/windows (but i have kde cursor!). Also, no combination of keyboard escapes will let me back to terminal.... so its yanking the power cord from the wall unfortunately.

A bit strange that it seems to be having path problems since /bin and /lib64 etc are definetly in my path. Wish I knew more about gdm ( or how to use sddm on el7).

Had any experience with installing into /usr/ ?

Alloysius, are you also the Aloysius (single 'l') who posted above?

I installed to /opt

I had the same black screen with plasma cursor and resolved it here.

Hope this helps.

Hi -

yes both are me but due to some insane logic, KDE forums username is not your login name, nor your account name, and there is no way to recover your account password on KDE forums with only your forum name (!!)

:sigh:

yes - I've used the runPlasma.sh script to test plasma that I built in /opt/ and that works fine. I'm more asking about why plasma5 fails to run when you use the default /usr/share/xsessions/plasma.desktop with the default target /usr/bin/startkde (which exists and is installed by plasma5).

In the mean time I await plasma5 copr from progdan with baited breath

Since a lot of the packages made it to epel, i wanted to check if there's any progress on this. Is there a repo for getting the Plasma 5 desktop working now ? Is the goal to have everything in epel eventually ?

Hi,

Kde 5.7 is out for most of the distros, any chance it will be available to Cent OS/RHEL community? I can't see any package update on Cent OS through EPEL. Really looking forward.

Thanks

~Alan

Any update on this yet?