Bug 329151 - Include paths from CMake macros are not correctly imported.
Summary: Include paths from CMake macros are not correctly imported.
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-23 11:48 UTC by Gregor Horst
Modified: 2023-02-11 03:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Horst 2013-12-23 11:48:17 UTC
KDevelop does no longer import the include paths given by the CMake Qt5 macros correctly. The latest released version handle them correctly. The bug seems to be introduced by the revision e9a542d6b68c622e2cfe55789a11d283ae58b828 .

Simplified example:
CMakeLists.txt:
[code]
cmake_minimum_required(VERSION 2.8.8)
project(Test)
set(CMAKE_AUTOMOC ON)
find_package(Qt5Widgets REQUIRED)
add_executable(test main.cpp)
qt5_use_modules(main Widgets)
[/code]
main.cpp:
[code]
#include <QApplication>
int main(int argc, char *argv[]){
    QApplication a(argc, argv);
    return a.exec();
}
[/code]

#include <QApplication> is correctly used by the GCC and CLang++, nut no longer recognized by current git version of KDevelop.


Reproducible: Always
Comment 1 Gregor Horst 2013-12-23 11:52:58 UTC
Small error in the sample code.
qt5_use_modules(main Widgets)
should be:
qt5_use_modules(test Widgets)

(I should simply copy my CMakeLists.txt next time...)
Comment 2 Milian Wolff 2013-12-23 14:01:24 UTC
The git commit you references does not change any behavior, I rather suspect it was the whole IncludePath* cleanup dones in  commits adb36605967c345e69c63ed63686e47bd01be53e and 686a54181199ed03358b063985339eb6265e9f27 .

Anyhow, this then probably uncovered a bug in the CMake support and we'll need to address that. If you want to help us, it would be awesome if you could create standalone macros which exhibit this behavior. I.e. a single CMakeLists.txt without external dependencies.
Comment 3 Andrew Crouthamel 2018-11-11 04:33:21 UTC
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!
Comment 4 Andrew Crouthamel 2018-11-21 04:42:36 UTC
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!
Comment 5 Justin Zobel 2023-01-12 01:58:17 UTC
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!
Comment 6 Bug Janitor Service 2023-01-27 05:07:44 UTC
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!
Comment 7 Bug Janitor Service 2023-02-11 03:52:24 UTC
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!