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
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 just
[: 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
QLibrary
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 or
Hi all,
Just a quick notice that due to Qt breaking their ABI it is now
necessary for build.kde.org (Jenkins) to initiate a rebuild of all
binaries.
This will take a long time to complete unfortunately, I suspect ~24 - 48 hours.
An excerpt of the failure log is below, prior to the rebuild.
https://codereview.qt-project.org/#change,39912
On Sun, Nov 25, 2012 at 11:54 AM, Ben Cooksley bcooks...@kde.org wrote:
Hi all,
Just a quick notice that due to Qt breaking their ABI it is now
necessary for build.kde.org (Jenkins) to initiate a rebuild of all
binaries.
This will take a long
On Nov. 22, 2012, 7:45 p.m., David Faure wrote:
This probably needs a #ifdef on the kdelibs version number, then, since
apparently kde-baseapps master only requires kdelibs-4.8...
It says find_package(KDE4 4.8.0 REQUIRED). Not sure why not 4.9 at least,
but that wouldn't help
As it turns out, the correction in this case was the cause of this
breakage. Somehow the original breakage (which was built and deployed
by build.kde.org 3 builds ago) did not have any impact upon the
system, yet the revert of the breakage caused this.
Because as the Gerrit text wrote: it
Hi all,
Just a quick notice that due to Qt breaking their ABI it is now
necessary for build.kde.org (Jenkins) to initiate a rebuild of all
binaries.
This will take a long time to complete unfortunately, I suspect ~24 - 48 hours.
An excerpt of the failure log is below, prior to the rebuild.
On segunda-feira, 26 de novembro de 2012 00.54.39, Ben Cooksley wrote:
Just a quick notice that due to Qt breaking their ABI it is now
necessary for build.kde.org (Jenkins) to initiate a rebuild of all
binaries.
This will take a long time to complete unfortunately, I suspect ~24 - 48
hours.
https://codereview.qt-project.org/#change,39912
On Sun, Nov 25, 2012 at 11:54 AM, Ben Cooksley bcooks...@kde.org wrote:
Hi all,
Just a quick notice that due to Qt breaking their ABI it is now
necessary for build.kde.org (Jenkins) to initiate a rebuild of all
binaries.
This will take a long
11 matches
Mail list logo