Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMake configuration fails with Qt 6.8.0 #255

Open
petrmanek opened this issue Oct 15, 2024 · 2 comments
Open

CMake configuration fails with Qt 6.8.0 #255

petrmanek opened this issue Oct 15, 2024 · 2 comments

Comments

@petrmanek
Copy link

Hello! I recently switched to Qt 6.8 and started encountering a failure during cmake configuration, which makes it impossible to build anything.

Here is basic information about my setup:

  • I am building QuickQanava from source through cmake's add_subdirectory() command. My program is later linked with the QuickQanava target.
  • I am using QuickQanava 6.4.1, although I have verified that the same error also happens with version 6.5.0.
  • My compiler is clang 18.1.8.
  • My cmake version is 3.30.5.
Building QuickQanava for Qt6
QuickQanava building with Qt6
src/CMakeLists.qt6.txt
CMake Error at /usr/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:227 (string):
  string sub-command SUBSTRING requires four arguments.
Call Stack (most recent call first):
  /usr/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:184 (_qt_internal_wrap_cpp)
  /usr/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:299 (qt6_wrap_cpp)
  lib/quickqanava/src/CMakeLists.qt6.txt:10 (qt_wrap_cpp)
  lib/quickqanava/src/CMakeLists.txt:95 (include)


CMake Error at /usr/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:265 (message):
  qt6_wrap_cpp: Unknown file extension: ".".
Call Stack (most recent call first):
  /usr/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:184 (_qt_internal_wrap_cpp)
  /usr/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:299 (qt6_wrap_cpp)
  lib/quickqanava/src/CMakeLists.qt6.txt:10 (qt_wrap_cpp)
  lib/quickqanava/src/CMakeLists.txt:95 (include)


-- Configuring incomplete, errors occurred!

It seems that source of the problem is invalid syntax on this line, which means that this issue could be related to #229.

Please advise.

@petrmanek
Copy link
Author

Looking at open PR's, it seems that #253 may be able to address this issue.

@petrmanek
Copy link
Author

@cneben Can we please get some response from maintainers? This issue has been open for several months at this point, and is (in my humble opinion) easily remedied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant