https://bugs.kde.org/show_bug.cgi?id=411580
Antonio Rojas <aro...@archlinux.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aro...@archlinux.org
--- Comment #3 from Antonio Rojas <aro...@archlinux.org> ---
This is only reproducible if you compile *without* krunner. Here's what's going
on:
- If you *don't* have krunner: cmake calls find_package(ECM 5.48.0), from
kdeconnect's CMakelists. Since 5.48.0>5.38.0, ECM sets
CMAKE_LIBRARY_OUTPUT_DIRECTORY
to ${CMAKE_BINARY_DIR}/bin (see KDECmakeSettings), and all binaries are
installed there - which causes this conflict between the kdeconnect dir used by
plugins and the kdeconnect binary.
- If you *do* have krunner: after all of the above, krunner calls plasma, which
in turn calls kpackage, which in turn calls find_package(ECM 1.6.0). Since
1.6.0<5.38.0, ECM *unsets* the CMAKE_LIBRARY_OUTPUT_DIRECTORY that was
previously set - so now each binary is installed to its own dir and they don't
conflict.
So this is a real bug, which is only masked by krunner pulling an import of an
old version of ECM.
--
You are receiving this mail because:
You are watching all bug changes.
