https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #15 from Ahmad Samir ---
Git commit c070f3338da63feb0f81170608f9c5de76f98e3c by Ahmad Samir.
Committed on 14/06/2022 at 12:00.
Pushed by ahmadsamir into branch 'master'.
Adjust repo's own includes
Use ForwardingHeaders for public headers.
https://bugs.kde.org/show_bug.cgi?id=453759
Friedrich W. H. Kossebau changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=453759
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #12 from Friedrich W. H. Kossebau ---
Ah, right, yes, I only thought about building KSyntaxHighlighting itself, as
the bug report talks about in title and initial description.
Once it itself is built (if that works) and you build against
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #11 from Nicolas Arnaud-Cormos ---
I don't see how it will help me.
The problem is not necessary when building KSyntaxHighlighting (even if in my
case I'm also building it with C++20), but rather when using it in another
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #10 from Friedrich W. H. Kossebau ---
So a work-around for you might be to set the CMake C++ standard explicitly to
C++17 for that subdirectory with ksyntaxhighligting, to match what is
officially supported. Building the code with C++20
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #9 from Nicolas Arnaud-Cormos ---
Friedrich: Sorry, I wasn't clear, this is when integrating KSyntaxHighlighting
with another application - this one using C++20.
I did the integration with CMake/FetchContent.
At this point, you have 2
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #8 from Friedrich W. H. Kossebau ---
Nicolas: I am curious: given ksyntaxhighlighting itself is set to use C++17
during its build, does MSVC fail to react to that and still make C++20 headers
visible or even use them?
Or, when you say
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #7 from Friedrich W. H. Kossebau ---
Thanks to a shower thought I guess the problem is rather that the current
buildsystem setup for KSyntaxHighlighting generates the forward camelcase
headers directly in the build directory of the library,
https://bugs.kde.org/show_bug.cgi?id=453759
Friedrich W. H. Kossebau changed:
What|Removed |Added
CC||kosse...@kde.org
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #5 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/313
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #4 from Ahmad Samir ---
I think how the repo's headers are included in its own source files needs to be
cleaned up too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453759
Ahmad Samir changed:
What|Removed |Added
CC||a.samir...@gmail.com
--- Comment #3 from Ahmad
https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #2 from Nicolas Arnaud-Cormos ---
(In reply to Nicolas Fella from comment #1)
> case-insensitive filesystem strikes again :facepalm:
>
> the problem isn't so much ecm_generate_headers, rather it's that we want to
> install a header named
https://bugs.kde.org/show_bug.cgi?id=453759
Nicolas Fella changed:
What|Removed |Added
CC||nicolas.fe...@gmx.de
--- Comment #1 from
15 matches
Mail list logo
