skrooge pipelines fail on qt6

[Mark Penner]

https://api.kde.org/ecm/kde-module/KDEClangFormat.html

Don't check the `.clang-format` file in to git since you're using 
KDEClangFormat.

Re: skrooge pipelines fail on qt6

[Ingo Klöcker]

On Freitag, 3. Januar 2025 22:44:28 Mitteleuropäische Normalzeit Mark Penner 
wrote:
> https://api.kde.org/ecm/kde-module/KDEClangFormat.html
> 
> Don't check the `.clang-format` file in to git since you're using
> KDEClangFormat.

Either that or remove the line
"This file got automatically created by ECM, do not edit"
from the committed .clang-format file. Then KDEClangFormat shouldn't try to 
overwrite the existing .clang-format file.

Regards,
Ingo


signature.asc
Description: This is a digitally signed message part.

skrooge pipelines fail on qt6

[Stéphane MANKOWSKI]

Hi,

The skrooge pipelines on qt6 are failing with the following issue:

   *CMake Error at
   _install/share/ECM/kde-modules/KDEClangFormat.cmake:64
   (configure_file):*
   *Operation not permitted*

Example:
https://invent.kde.org/office/skrooge/-/jobs/2430964 



I don't know how to solve that. The build is working well at home.

Could you help me ?

Regards,
Stéphane

Re: Compile error in kcoreaddons

[Tomaz Canabrava]

mingw?
are you on windows?

On Tue, Dec 31, 2024 at 4:29 PM Thomas Höpping 
wrote:

> Hello,
> I just wanted to do some coding in a KDE application. Therefore I started
> to
> set up my development environment using kde-builder.
>
> I followed the instructions defined on the kde-builder web page.
> While compilation of kcoreaddons I get a build aboard.
> The error message is:
> /usr/include/qt6/QtCore/qglobal.h:13:12: fatal: ‘type_traits’ file not
> found
>
> The search using locate type_traits results in:
> /usr/i686-w64-mingw32/sys-root/mingw/include/c++/type_traits
> /usr/i686-w64-mingw32/sys-root/mingw/include/c++/bits/cpp_type_traits.h
> /usr/i686-w64-mingw32/sys-root/mingw/include/c++/experimental/type_traits
> /usr/i686-w64-mingw32/sys-root/mingw/include/c++/ext/type_traits.h
> /usr/i686-w64-mingw32/sys-root/mingw/include/c++/tr1/type_traits
> /usr/i686-w64-mingw32/sys-root/mingw/include/c++/tr2/type_traits
> /usr/include/c++/14/type_traits
> /usr/include/c++/14/bits/cpp_type_traits.h
> /usr/include/c++/14/experimental/type_traits
> /usr/include/c++/14/ext/type_traits.h
> /usr/include/c++/14/tr1/type_traits
> /usr/include/c++/14/tr2/type_traits
> /usr/include/qt6/QtCore/q20type_traits.h
> /usr/include/qt6/QtCore/qxptype_traits.h
> /usr/lib64/python3.13/site-packages/pyarrow/src/arrow/python/type_traits.h
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/type_traits
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/bits/cpp_type_traits.h
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/experimental/type_traits
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/ext/type_traits.h
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/tr1/type_traits
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/tr2/type_traits
> System details
> Fedora 41
> Could somebody give advice how to proceed?
> Regards
> Thomas
>
>
>

Re: Move Breeze to Framework

[Nicolas Fella]

Am 30.12.24 um 18:51 schrieb Nate Graham:

A long term concern I have is that it's messy and unpleasant to have
default styling data scattered across so many places. Ideally we'd be
able to centralize *all* data about a particular style in a single
repo, so that making changes is easy and that repo can be swapped out
for another one in the future.

I see an opportunity to move closer to that here. So my preference
would be to implement the proposal, but also:
- the default window decorations remain in Breeze


That part is problematic. The window decoration needs KDecoration, which
is not in Frameworks, and given that it's closely tied to KWin I'd argue
it shouldn't be.


- the default colors remain in Breeze, and are removed from KColorScheme
- breeze-icons is merged into Breeze

Then later we can investigate what it might take to haul the
Plasma-scoped Breeze visual theming (e.g splash screen, SDDM theme,
Plasma SVG theme) into that repo as well. But that can be a longer
term thing.

Nate