Kdelibs4 possesses an internal FindFlex.cmake file, which does not always functions. For example, trying to build digikam (version 3.5.0 or 4.0.0) leads to the following error: CMake Error at extra/kipi-plugins/panorama/CMakeLists.txt:10 (FLEX_TARGET): Unknown CMake command "FLEX_TARGET". As FindFlex does not provide the command FLEX_TARGET. On the other hand, cmake possesses its own FindFlex script, which works as it provides FLEX_TARGET. Digikam should either be made compatible with the script of the library it depends on, or kdelibs4 leave the probably more standard script of cmake be used. Reproducible: Always Steps to Reproduce: 1. Install digikam dependencies 2. Try to build digikam 3. The error happens at configure stage Actual Results: Digikam configure stage fails with the message: CMake Error at extra/kipi-plugins/panorama/CMakeLists.txt:10 (FLEX_TARGET): Unknown CMake command "FLEX_TARGET". Expected Results: Configure should complete. When suppressing FindFlex.cmake provided by kdelibs4, the script provided by cmake is used instead, and building digikam works. This can also be achieved by adjusting the priority of the path in which cmake select scripts.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!