https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #7 from Friedrich W. H. Kossebau <kosse...@kde.org> --- 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, which also is part of the include directories set up for the build, and before any system directories. So the preprocessor on searching to resolve #include <format> will simply first come across the "Format" file in the library build dir, and then things go boom. So the generated headers need to be placed outside of the include directories, or, in this case due to other planned usages like from the examples referencing the generated forward headers, be placed into a subdir matching the prefix dir as used in the installed case. So the part of https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/313 which adds the "OUTPUT_DIR" argument to the ecm_generate_headers call should improve things and avoid the name collision. -- You are receiving this mail because: You are watching all bug changes.
