Re: ECM unittest fails, why?

On Tue, Mar 24, 2020 at 7:48 PM Friedrich W. H. Kossebau wrote: > > Am Montag, 23. März 2020, 20:30:59 CET schrieb Friedrich W. H. Kossebau: > > Am Sonntag, 22. März 2020, 10:50:39 CET schrieb David Faure: > > > The CI for ECM has been failing ever since the tests were re-enabled. > > > > > >

D26752: ECMAddAppIcon: Do not warn about mac and window icons if isnt a OS specific build

bcooksley requested changes to this revision. bcooksley added a comment. Christophe is correct here, it is worth warning developers about these issues regardless of the platform, so they can get the code ready for those platforms and test everything in their local environment as much as

D23262: disable autouic again - it breaks builds

bcooksley removed a subscriber: fusitter. REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D23262 To: sitter, apol, nicolasfella, cullmann Cc: bcooksley, kde-frameworks-devel, kde-buildsystem, LeGast00n, GB_2, bencreasy, michaelh, ngraham, bruns, fusitter

Eliminating the last CI Failures

Hi all, For a while now we've had a couple of projects which have been persistently failing on all platforms, which it would be nice to get fixed. If someone would like to take a look into one of the following, it would be appreciated, and would help to eliminate the last couple of items from

D21313: Create specific directory for Qt logging categories file

bcooksley added a comment. The Binary Factory uses the tooling shipped as part of the KDE SDK (which always builds everything from scratch, and I don't know if part of that includes ECM, hence why the issue doesn't show up there). The CI system on the other hand uses it's own tooling

D21313: Create specific directory for Qt logging categories file

bcooksley added a comment. This change appears to be responsible for all Android builds being broken. See https://build.kde.org/view/Failing/ Could someone take a look please? REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D21313 To: mlaurent,

D21381: use org.freedesktop.appstream-glib package to validate appstream data

bcooksley added a comment. Aleix is correct, Flatpak commands are not possible within the CI environment (as Docker is heavily locked down, and the containerisation and other isolation measures that Flatpak tries to take are locked out as a consequence) Not to mention that Flatpak is Linux

D19075: Fix FindEGL

bcooksley added a comment. If someone could please trigger all of the Dependency Builds for FreeBSD once this has been landed that would be appreciated: https://build.kde.org/view/Failing/ REPOSITORY R240 Extra CMake Modules BRANCH master REVISION DETAIL

D18960: Add compile check to FindEGL

bcooksley added a comment. /usr/local/bin/gmake -f CMakeFiles/cmTC_fd24d.dir/build.make CMakeFiles/cmTC_fd24d.dir/build gmake[1]: Entering directory '/usr/home/jenkins/kwayland/build/CMakeFiles/CMakeTmp' Building CXX object CMakeFiles/cmTC_fd24d.dir/src.cxx.o /usr/bin/c++

Re: ECM tests not run by CI (Re: KDE Frameworks 5.55.0)

ed into it, and here's the reason why: > > > > [ci-tooling repo] > > commit 45ff1bc4ecb18ad71ad0570f7e838d1ae7cab2e2 > > Author: Ben Cooksley > > Date: Wed Sep 27 22:04:05 2017 +1300 > > > > Revoke test execution for extra-cmake-modules across a

D18547: Don't enable -Wzero-as-null-pointer-constant on apple clang

bcooksley added a comment. This change is somewhat urgent - as can be seen at https://binary-factory.kde.org/view/MacOS/ all Mac builds are currently broken due to this issue. REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D18547 To: vonreth, aacid,

D15068: Bindings: Correct handling of sources containing utf-8

bcooksley added a comment. The code itself looks fine to me - the change on line 752 is to allow handling of macOS / Windows line endings in addition to just Unix line endings I presume? REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D15068 To: bruns,

Re: ECM Behaviour: Setting QT_PLUGIN_PATH on Windows

On Sat, 8 Sep 2018, 20:12 David Faure, wrote: > On vendredi 31 août 2018 10:50:53 CEST Ben Cooksley wrote: > > On Tue, Aug 28, 2018 at 10:35 PM Ben Cooksley wrote: > > > Hi all, > > > > Hi all, > > > > > We currently have a severe bug in ECM's Add

D15070: Bindings: Query the install directory from python

bcooksley added a comment. We could, however that would not help people installing it as a regular user, rather than as root. If I run this right now, as an unprivileged user, I get the following path returned: >>> sysconfig.get_python_lib( plat_specific=True,standard_lib=False )

D8256: Add _XOPEN_SOURCE to C definitions

bcooksley added subscribers: FreeBSD, bcooksley. bcooksley added a comment. This change appears to have resulted in a severe regression of builds on FreeBSD. Any ideas? REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D8256 To: awilcox, alexmerry,

Re: ECM Behaviour: Setting QT_PLUGIN_PATH on Windows

On Tue, Aug 28, 2018 at 10:35 PM Ben Cooksley wrote: > > Hi all, Hi all, > > We currently have a severe bug in ECM's AddTest macro due to it's > behaviour around the setting of QT_PLUGIN_PATH. On Windows it would > appear that the code in ECMAddTest mangles the environment va

D15070: Bindings: Query the install directory from python

bcooksley added a comment. Please ensure that wherever it is installed to ends up within CMAKE_INSTALL_PREFIX otherwise this will end up failing on the CI system. The CI system takes care of setting PYTHONPATH accordingly to ensure resources are found. REPOSITORY R240 Extra CMake

D11176: Don't call PythonInterp.cmake in KF5I18NMacros.

bcooksley added a comment. Restricted Application edited subscribers, added: kde-frameworks-devel; removed: Frameworks. This change has broken the build of all projects that make use of pmap resources on Windows, as the Python path at build time is not necessarily the path at install time

D9299: Introduce INSTALL_PREFIX_SCRIPT to easily set up prefixes

bcooksley added a comment. Depending on the end goal of this you may wish to also set the following environment variables: CMAKE_PREFIX_PATH: to help guide CMake to look here in addition to system prefixes PKG_CONFIG_PATH: to help pkg-config find *.pc files QMAKEFEATURES: to

D8979: ecm_add_test: Use proper path sep on Windows

bcooksley accepted this revision. bcooksley added a comment. Looks fine to me. REPOSITORY R240 Extra CMake Modules BRANCH master REVISION DETAIL https://phabricator.kde.org/D8979 To: kfunk, dfaure, cgiboudeaux, bcooksley Cc: #windows, #frameworks, #build_system

T6480: Some calligra tests fail

bcooksley added a comment. No worries TASK DETAIL https://phabricator.kde.org/T6480 To: danders, bcooksley Cc: bcooksley, #build_system, danders, sysadmin, scarlettclark, blazquez

T6480: Some calligra tests fail

bcooksley added a comment. I suspect that's a bug in your script as there is a space in the workspace directory used by the CI system. Can you check all places where paths are inserted are quoted? TASK DETAIL https://phabricator.kde.org/T6480 To: bcooksley Cc: bcooksley, #build_system,

T6480: Some calligra tests fail

bcooksley moved this task from External: Active to External: Awaiting Response on the Sysadmin board. bcooksley added a comment. Please provide more detail as to the exact tests which are failing (links to build.kde.org would be great) TASK DETAIL https://phabricator.kde.org/T6480

D6073: Don't enable strict iterators on MSVC

bcooksley abandoned this revision. REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D6073 To: bcooksley, kfunk Cc: kfunk, arrowdodger, #frameworks, #build_system

D6073: Don't enable strict iterators on MSVC

bcooksley created this revision. Restricted Application added projects: Frameworks, Build System. Restricted Application added subscribers: Build System, Frameworks. REVISION SUMMARY Currently we've found that strict iterators as available in MSVC, with certain codebases such as Threadweaver

Re: Extremely poor quality of KWave's build system

possibility of "defending" themselves. >> >> I think a more positive way would have been to stop before you get ultra- >> frustrated and say something like "I can't get this to work, please have a >> look, if this doesn't get fixed in X days we may have to thi

Re: Extremely poor quality of KWave's build system

On Wed, May 24, 2017 at 9:37 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dimarts, 23 de maig de 2017, a les 19:53:29 CEST, Ben Cooksley va escriure: >> Hi all, >> >> I've been working on the new CI system recently, and as part of this >> have run into a fe

Re: Extremely poor quality of KWave's build system

On Wed, May 24, 2017 at 8:36 PM, Luca Beltrame wrote: > Il giorno Tue, 23 May 2017 23:37:25 +0200 > Albert Astals Cid ha scritto: > >> On the actual problem, as a workaround, have you tried "apt-get >> build-dep kwave" or the "synonymous" command in whatever OS

Extremely poor quality of KWave's build system

privileges from this point forward as I don't want to waste any further time on this. Regards, Ben Cooksley KDE Sysadmin

D5489: Sanitizers: Don't use GCC-like flags for e.g. MSVC

bcooksley accepted this revision. bcooksley added a comment. Looks good to me - thanks for taking this on, it'll make getting CI working for Windows much easier. REPOSITORY R240 Extra CMake Modules BRANCH master REVISION DETAIL https://phabricator.kde.org/D5489 To: kfunk, aacid,

Re: Review Request 129117: Adds KF5Purpose and Kirigami to the default build

> On Nov. 5, 2016, 9:14 a.m., David Faure wrote: > > Ship It! > > David Faure wrote: > I withdraw my approval. Please revert. > I just noticed that these modules have been added for the "frameworks" > module-set. This doesn't make sense, they are not part of frameworks. When I > type

Re: Review Request 128779: Teach KDECompilerSettings about clang-cl, a mode of Clang compiler that simulates MSVC.

> On Oct. 8, 2016, 9:09 a.m., Ben Cooksley wrote: > > This code as it stands failed on the CI system and proceeded to break all > > Frameworks builds. > > Please re-review the code and ensure that no action is taken for GCC based > > compilers. > > Gleb Popo

Re: Review Request 128779: Teach KDECompilerSettings about clang-cl, a mode of Clang compiler that simulates MSVC.

to break all Frameworks builds. Please re-review the code and ensure that no action is taken for GCC based compilers. - Ben Cooksley On Oct. 8, 2016, 6:41 a.m., Gleb Popov wrote: > > --- > This is an automatically generat

ECM Breakage: Compilation failure for GCC

Hi all, It appears that commit 4b8e8dcc8856d8f438860783e7641d02d1c05630 to ECM broke the whole CI system for all Qt 5 / Frameworks builds. I've therefore reverted it. Regards, Ben Cooksley KDE Sysadmin

Re: The return of ASAN issues

On Mon, Jun 13, 2016 at 6:25 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dimarts, 31 de maig de 2016, a les 18:49:29 CEST, Ben Cooksley va escriure: >> On Tue, May 31, 2016 at 9:36 AM, Albert Astals Cid <aa...@kde.org> wrote: >> > El dilluns, 30 de maig de

Re: The return of ASAN issues

On Tue, May 31, 2016 at 9:36 AM, Albert Astals Cid <aa...@kde.org> wrote: > El dilluns, 30 de maig de 2016, a les 19:42:38 CEST, Ben Cooksley va escriure: >> Hi all, >> >> As you may recall, some time ago the CI scripts were adapted to >> forcibly inject ASAN

Re: The return of ASAN issues

On Mon, May 30, 2016 at 10:51 PM, Friedrich W. H. Kossebau <kosse...@kde.org> wrote: > Hi, Hi Friedrich, > > Am Montag, 30. Mai 2016, 19:42:38 CEST schrieb Ben Cooksley: >> As you may recall, some time ago the CI scripts were adapted to >> forcibly inject ASAN into

The return of ASAN issues

Hi all, As you may recall, some time ago the CI scripts were adapted to forcibly inject ASAN into all test processes launched on the CI system to fix Marble's tests, as Marble does not use ECM and thus does not enable ASAN as a result. Unfortunately this has bad effects with certain processes,

Re: [Digikam-devel] [Kde-pim] Akonadi Contact library: Targets not properly exported

On Thu, Apr 28, 2016 at 11:32 PM, Aleix Pol <aleix...@kde.org> wrote: > On Thu, Apr 28, 2016 at 8:28 AM, Ben Cooksley <bcooks...@kde.org> wrote: >> On Thu, Apr 28, 2016 at 7:22 AM, Stephen Kelly <steve...@gmail.com> wrote: >>> Ben Cooksley wrote: >>&g

Re: [Digikam-devel] [Kde-pim] Akonadi Contact library: Targets not properly exported

On Wed, Apr 27, 2016 at 7:11 PM, Stephen Kelly <steve...@gmail.com> wrote: > Ben Cooksley wrote: > >> It would be appreciated if you jointly investigated why this isn't >> working. > > Hi, Hi Stephen, > > Sorry for not being active on this before. &g

Re: [Digikam-devel] [Kde-pim] Akonadi Contact library: Targets not properly exported

On Sat, Apr 9, 2016 at 8:07 PM, Christophe Giboudeaux <cgiboude...@gmx.com> wrote: > On samedi 9 avril 2016 08:53:51 CEST Ben Cooksley wrote: >> On Sat, Apr 9, 2016 at 12:38 AM, Gilles Caulier >> >> <caulier.gil...@gmail.com> wrote: >> > H

Re: [Digikam-devel] [Kde-pim] Akonadi Contact library: Targets not properly exported

uild. >> >> >> https://build.kde.org/job/digikam%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/68/console >> >> I do notice KDE_INSTALL_INCLUDEDIR_KF5 in kdepimlibs is likely what puts >> in this KF5 folder? >> >> I do not know who is responsible here,

Re: [Kde-pim] Akonadi Contact library: Targets not properly exported

On Thu, Mar 31, 2016 at 11:44 PM, Christophe Giboudeaux <cgiboude...@gmx.com> wrote: > On mercredi 30 mars 2016 20:19:29 CEST Ben Cooksley wrote: >> On Tue, Mar 29, 2016 at 10:46 PM, Sandro Knauß <skna...@kde.org> wrote: >> >> Those are the header generation and

Re: [Kde-pim] Akonadi Contact library: Targets not properly exported

missing in this case is the include path specification for the KF5::AkonadiContact target which CMake provides. > > Regards, > > sandro Cheers, Ben > > Am Dienstag, 29. März 2016, 14:48:38 CEST schrieb Ben Cooksley: >> Hi PIM developers, >> >> It wo

Re: Plasma Workspace - Improperly exporting targets

On Wed, Mar 30, 2016 at 3:19 AM, Aleix Pol <aleix...@kde.org> wrote: > On Tue, Mar 29, 2016 at 11:07 AM, Ben Cooksley <bcooks...@kde.org> wrote: >> On Tue, Mar 29, 2016 at 7:03 PM, Martin Graesslin <mgraess...@kde.org> wrote: >>> On Tuesday, March 29, 2016

Re: Plasma Workspace - Improperly exporting targets

On Tue, Mar 29, 2016 at 7:03 PM, Martin Graesslin <mgraess...@kde.org> wrote: > On Tuesday, March 29, 2016 10:13:02 AM CEST Ben Cooksley wrote: >> Hi Plasma Devs, >> >> It would appear Plasma Workspace is improperly exporting it's targets, >> leading to build fa

Akonadi Contact library: Targets not properly exported

Hi PIM developers, It would appear the Akonadi Contact library does not properly export it's targets, or does so in a manner in which valid include paths for Akonadi libraries are not included in this. Could someone please take a look? This causes Digikam to fail to build on the CI system,

KHotKeys: Plugin metadata missing?

Hi Plasma Devs, It would seem that KHotkeys now fails to build, due to either: a) Missing plugin metadata b) Missing CMake target dependencies between the automoc task and the task that generates the plugin metadata. Could someone correct this please?

Re: Plasma Workspace - Improperly exporting targets

On Tue, Mar 29, 2016 at 10:59 AM, Stephen Kelly <steve...@gmail.com> wrote: > Ben Cooksley wrote: > >> Hi Plasma Devs, >> >> It would appear Plasma Workspace is improperly exporting it's targets, >> leading to build failures. This particularly affects Apper, w

Plasma Workspace - Improperly exporting targets

Hi Plasma Devs, It would appear Plasma Workspace is improperly exporting it's targets, leading to build failures. This particularly affects Apper, which is unable to build on the CI system as a result. Please ensure when exporting targets / finding libraries that the full path to the library is

kdepim-runtime: Missing CMake dependency targets

Hi, It seems some internal targets within kdepim-runtime are missing appropriate dependency target settings. Please see https://build-sandbox.kde.org/job/kdepim-runtime%20master%20kf5-qt5/lastFailedBuild/PLATFORM=Linux,compiler=gcc/console Could someone please investigate? Thanks, Ben

Re: building kio on Mac

On Mon, Jun 8, 2015 at 7:13 PM, David Faure fa...@kde.org wrote: That wasn't very constructive/positive... Sorry, i've spent way too much time fighting with the Qt folks on this one. On Monday 08 June 2015 15:22:20 Ben Cooksley wrote: The Qt developers didn't want to provide any

Re: Challenge for real experts: why does cmake on CI not use automoc for a certain file?

On Sat, Jun 6, 2015 at 10:07 PM, Alex Merry alex.me...@kde.org wrote: On Friday 05 June 2015 00:58:30 Friedrich W. H. Kossebau wrote: you are a cmake and KDE buildsystem expert? Prove that yourself and improve the world for others ;) Or, indeed, work towards becoming such an expert... Here

Re: building kio on Mac

On Sat, Jun 6, 2015 at 9:41 PM, Alex Merry alex.me...@kde.org wrote: On Wednesday 27 May 2015 06:56:29 Allen Winter wrote: On Tuesday, May 26, 2015 09:12:13 AM Scarlett Clark wrote: On Tuesday, May 26, 2015 12:06:22 PM Allen Winter wrote: % kdesrc-build kio Could not locate file

Re: Severe behavioural change regressions in release branch

On Sat, Oct 25, 2014 at 7:14 PM, Stephen Kelly steve...@gmail.com wrote: Ben Cooksley wrote: On Sat, Oct 25, 2014 at 5:44 AM, Stephen Kelly steve...@gmail.com wrote: Is build.kde.org now using the release branch of cmake.git instead of the next branch? When/why did that change

Re: Severe behavioural change regressions in release branch

, Oct 25, 2014 at 08:50:12 +1300, Ben Cooksley wrote: On Sat, Oct 25, 2014 at 5:44 AM, Stephen Kelly steve...@gmail.com wrote: Is build.kde.org now using the release branch of cmake.git instead of the next branch? When/why did that change? This was changed around about http

Re: Severe behavioural change regressions in release branch

On Sat, Oct 25, 2014 at 5:44 AM, Stephen Kelly steve...@gmail.com wrote: Ben Cooksley wrote: Hi all, It would appear that CMake 3.0 to 3.1 introduces a colossal change in behaviour. This change totally breaks all KDE projects which use Extra-CMake-Modules, as necessary headers are no longer

Severe behavioural change regressions in release branch

of compatibility breakage would be a release blocker. Regards, Ben Cooksley KDE Sysadmin ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem

Re: Severe behavioural change regressions in release branch

On Fri, Oct 24, 2014 at 10:05 AM, Ben Cooksley bcooks...@kde.org wrote: Hi all, It would appear that CMake 3.0 to 3.1 introduces a colossal change in behaviour. This change totally breaks all KDE projects which use Extra-CMake-Modules, as necessary headers are no longer installed. This has

Re: Severe behavioural change regressions in release branch

On Fri, Oct 24, 2014 at 10:41 AM, Bill Hoffman bill.hoff...@kitware.com wrote: On 10/23/2014 5:11 PM, Ben Cooksley wrote: And it would seem that the CMake developers prefer to live in their own closed off little bubble. Hi Bill, Sorry about that. We just want to avoid spam. I have

Re: Severe behavioural change regressions in release branch

On Fri, Oct 24, 2014 at 10:11 AM, Ben Cooksley bcooks...@kde.org wrote: On Fri, Oct 24, 2014 at 10:05 AM, Ben Cooksley bcooks...@kde.org wrote: Hi all, It would appear that CMake 3.0 to 3.1 introduces a colossal change in behaviour. This change totally breaks all KDE projects which use Extra

Gwenview CI failure

Hi all, For some time now (since the Baloo functionality merge) Gwenview has failed to build on the CI system. See http://build.kde.org/view/FAILED/job/gwenview_master/206/consoleText for the build log. This appears to be due to Baloo using KFileMetaData includes, but not properly specifying

Re: Build failed in Jenkins: kdelibs_frameworks_qt5 #1806

On Mon, Dec 2, 2013 at 1:28 PM, David Faure fa...@kde.org wrote: On Sunday 01 December 2013 23:43:02 KDE CI System wrote: -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY --

Regression in CMake breaking builds

Hi all, It appears that a recent update to CMake on build.kde.org has broken a number of KDE projects, resulting in them now failing to build. An example can be found here: http://build.kde.org/view/FAILED/job/kdevplatform_master/560/consoleText The following projects appear to be affected at

Review Request 110843: Ensure we actually have Qwt 5 by looking for a header present only in Qwt 5

--- This fixes the build failures on Jenkins by looking for a header specific to Qwt 5, instead of a general Qwt header. Diffs - applets/kdeobservatory/cmake/modules/FindQwt.cmake 7045388 Diff: http://git.reviewboard.kde.org/r/110843/diff/ Testing --- Thanks, Ben Cooksley

Re: KDE Workspace broken due to upstream CMake changes

On Fri, May 31, 2013 at 12:24 AM, Stephen Kelly steve...@gmail.com wrote: Stephen Kelly wrote: Ben Cooksley wrote: Hi Alex, Can someone more familiar with the CMake community please inform them of this regression? http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/46742

Re: KDE Workspace broken due to upstream CMake changes

Hi Alex, Can someone more familiar with the CMake community please inform them of this regression? It is breaking the KDE Continuous Integration system - i'd appreciate being informed once the fix has landed in their Git repository, so we can deploy it. Regards, Ben

KDE Workspace broken due to upstream CMake changes

for XkbLockModifiers in X11 - not found Regards, Ben Cooksley ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem

Re: KDE Workspace broken due to upstream CMake changes

On Tue, May 28, 2013 at 7:37 AM, Alexander Neundorf neund...@kde.org wrote: On Monday 27 May 2013, Rolf Eike Beer wrote: Am 27.05.2013 09:13, schrieb Ben Cooksley: Hi all, It seems that a recent upstream change in CMake has now broken the build of KDE Workspace. Can someone please fix

Re: KDE Workspace broken due to upstream CMake changes

On Tue, May 28, 2013 at 12:51 AM, Rolf Eike Beer k...@opensource.sf-tec.de wrote: Am 27.05.2013 09:13, schrieb Ben Cooksley: Hi all, It seems that a recent upstream change in CMake has now broken the build of KDE Workspace. Can someone please fix or prod CMake upstream into revising

Re: qt4 vs qt5 build for dependencies

On Fri, Apr 5, 2013 at 10:27 PM, David Faure faure+bluesyst...@kde.org wrote: When I ported attica, soprano, libdbusmenu-qt and other such kdesupport- level dependencies to Qt5, I used find_package(Qt5Core QUIET) if (Qt5Core_FOUND) message(STATUS Building with Qt5 support) ... else()

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Fri, Feb 8, 2013 at 6:38 AM, Alexander Neundorf neund...@kde.org wrote: On Thursday 07 February 2013, Ben Cooksley wrote: On Thu, Feb 7, 2013 at 7:34 AM, Alexander Neundorf neund...@kde.org wrote: On Tuesday 05 February 2013, Alexander Neundorf wrote: On Monday 04 February 2013, Ben

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Fri, Feb 8, 2013 at 11:16 AM, Alexander Neundorf neund...@kde.org wrote: On Thursday 07 February 2013, Ben Cooksley wrote: On Fri, Feb 8, 2013 at 6:38 AM, Alexander Neundorf neund...@kde.org wrote: On Thursday 07 February 2013, Ben Cooksley wrote: On Thu, Feb 7, 2013 at 7:34 AM, Alexander

Re: Problems with ECM / FindKDE4Internal and plasma-framework

On Thu, Feb 7, 2013 at 7:34 AM, Alexander Neundorf neund...@kde.org wrote: On Tuesday 05 February 2013, Alexander Neundorf wrote: On Monday 04 February 2013, Ben Cooksley wrote: Hi all, Currently the KDE CI system is unable to build the newly created 'plasma-framework' repository

Problems with ECM / FindKDE4Internal and plasma-framework

Hi all, Currently the KDE CI system is unable to build the newly created 'plasma-framework' repository. Through some debugging I have determined that although all appropriate environment variables are set correctly (to the best of my knowledge) it seems that CMake is simply blind, or something

[kdelibs/KDE/4.10] cmake/modules: Ensure that the pkgconfig material is kept far away from the proper CMake logic.

Git commit 0f09cc362819d7818f7ac95ab6a4b55912390011 by Ben Cooksley. Committed on 06/01/2013 at 08:14. Pushed by bcooksley into branch 'KDE/4.10'. Ensure that the pkgconfig material is kept far away from the proper CMake logic. This fixes build failures for all projects which use kipi

Re: [kdepimlibs] /: Interim hack to make everything which depends on kdepimlibs build again.

On Thu, Dec 20, 2012 at 9:02 PM, Andreas Pakulat ap...@gmx.de wrote: Hi, Hi, On Thu, Dec 20, 2012 at 1:11 AM, Ben Cooksley bcooks...@kde.org wrote: Git commit f9ea1c7b4fb351a4da16b386c23f15d6c109728a by Ben Cooksley. Committed on 20/12/2012 at 01:11. Pushed by bcooksley into branch 'master

[kdepimlibs] /: Interim hack to make everything which depends on kdepimlibs build again.

Git commit f9ea1c7b4fb351a4da16b386c23f15d6c109728a by Ben Cooksley. Committed on 20/12/2012 at 01:11. Pushed by bcooksley into branch 'master'. Interim hack to make everything which depends on kdepimlibs build again. A proper solution is needed from the CMake folks, but I don't see consensus

kdepimlibs dependency on nepomuk-core breaks build for Calligra and kdeplasma-addons

Hi all, Currently build.kde.org is unable to successfully complete builds of kdeplasma-addons and Calligra due to recent changes in kdepimlibs. These changes are a port from Nepomuk (part of kdelibs) to NepomukCore (a seperate repository). As kdepimlibs uses the *Config.cmake method of exporting

Re: kdepimlibs dependency on nepomuk-core breaks build for Calligra and kdeplasma-addons

On Tue, Dec 18, 2012 at 8:14 AM, Alexander Neundorf neund...@kde.org wrote: On Monday 17 December 2012, Ben Cooksley wrote: Hi all, Currently build.kde.org is unable to successfully complete builds of kdeplasma-addons and Calligra due to recent changes in kdepimlibs. These changes are a port

Another CMake regression?

Hi all, It seems that following a recent CMake build from latest sources that the configure time for Calligra has severely regressed. It now takes in excess of 1 hour to complete the configure process, which is disrupting the operation of build.kde.org. Timestamped output: 14:45:29 -- cstester

KDevelop and Grantlee

Hi all, Currently build.kde.org is having some issues when building all KDevelop related projects (master branch) after kdevplatform. The build for various elements in them always fails with an error message indicating it is unable to find -lgrantlee_core. Is there something which should be done

Changing compiler options

Hi all, Recently build.kde.org ran into some problems with building libkdcraw, due to CMake using the -std=iso9899:1990 option with GCC. It seems that this appears to be incompatible with LCMS' use of inline functions. The build log can be viewed at

Re: Severe test regression in Kate?

Hi all, I will be reverting commit cd8a8d6d3914ce8a72f252b054073193b97dd0a7 in kate in 24 hours unless a fix is provided. The issue it introduces, especially with php files is particularly disruptive to user workflow. (I don't understand exactly how a broken Javascript syntax file can affect PHP

Re: Severe test regression in Kate?

Ben Cooksley wrote: Hi all, I will be reverting commit cd8a8d6d3914ce8a72f252b054073193b97dd0a7 in kate in 24 hours unless a fix is provided. The issue it introduces, especially with php files is particularly disruptive to user workflow. (I don't understand exactly how a broken

Fwd: Severe test regression in Kate?

Forwarding to kde-buildsystem, got no response from kwrite-devel... -- Forwarded Message -- Hi all, It seems that following commit cd8a8d6d3914ce8a72f252b054073193b97dd0a7, test #22 (kate-bug294241_test) has severely regressed. Further, it completely blocks build.kde.org when it executes (as it

Review Request: Fix Kalzium build and cleanup CMake warnings during Kalzium configuration by CMake

- KalziumConfigureChecks.cmake cef3d45 compoundviewer/CMakeLists.txt b2b7e6c src/CMakeLists.txt 47ebbd1 Diff: http://git.reviewboard.kde.org/r/103209/diff/diff Testing --- Now compiles. Thanks, Ben Cooksley ___ Kde-buildsystem mailing list Kde

Phonon's failure to detect Pulseaudio

Hi all, Currently my system (which has Pulseaudio enabled - version 0.9.21) with current Phonon master is NOT able to find Pulseaudio. As I need Pulseaudio in order to use my Bluetooth headset, it is highly irritating for this to have occurred. Tracing back, I found that this breakage occurred

Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)

2011/5/22 Dirk Mueller muel...@kde.org: On Saturday 21 May 2011, Eric Hameleers wrote: The turn of events with KDE 4.7.x is most unfortunate. I noticed an explosion of source tarballs. Yes, I started to resemble the git layout in the tarballs, given that I had a pain in the ass of work to

Re: KDEUtils build broken for extended period of time

On Mon, Jul 12, 2010 at 6:52 PM, Michael Zanetti michael_zane...@gmx.net wrote: Hi Ben, On Sunday 11 July 2010 13:30:11 Ben Cooksley wrote: Is there any reason why it has not been possible to build kdeutils for some time? ( couple of days at least ). Going back to a previously working

KDEUtils build broken for extended period of time

Hi all, Is there any reason why it has not been possible to build kdeutils for some time? ( couple of days at least ). Going back to a previously working KDEUtils revision isn't sufficient to fix it either, so I suspect it is caused by a change in another module, which concurs with the following

Broken compilation of KDENetwork module for excessive period of time due to Kopete

the KDENetwork build system approximately 6 times, and neither time has fixed the issue. Please CC me, since I am not subscribed. Regards, Ben Cooksley System Settings Maintainer KDE Community Forums Administrator ___ Kde-buildsystem mailing list Kde