Bug 388077 - Projects window no longer shows build targets - unable to add specific build targets to Build Sequence anymore
Summary: Projects window no longer shows build targets - unable to add specific build ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: CMake (show other bugs)
Version: 5.2.1
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-20 15:23 UTC by Maciej Mrozowski
Modified: 2022-12-10 05:17 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Mrozowski 2017-12-20 15:23:31 UTC
Steps to reproduce:
1. Open CMake project with KDevelop
2. Try adding specific build target to Build Sequence

Step 2 is no longer possible (it used to work) - executable CMake targets are not listed in "Projects" window.
CMake target discovery works because those executable targets can be selected in Run->Configure Launches. In Projects windows, directories with executable targets also have appropriate icon ("play" button).

This is strange since I think it used to work fine on this Fedora, rather recently, perhaps even with the same version of kdevelop. Also on my other system (Gentoo), where I also have kdevelop-5.2.1, I don't recall having such issue. Yet, here we are.
Any ideas how to debug this?
Comment 1 Maciej Mrozowski 2017-12-22 02:38:58 UTC
And on my Gentoo, with the same kdevelop-5.2.1, but different CMake, it shows all executable targets as expected.. + some make targets like 'uninstall', 'install', 'install/local', 'edit_cache'...
What is going on here?
Comment 2 Maciej Mrozowski 2017-12-27 19:28:40 UTC
And on my other Fedora 26 (but stable instead of testing), with the same kdevelop-5.2.1 installed, all is fine. Magic..
Comment 3 Maciej Mrozowski 2017-12-27 19:43:06 UTC
It's clearly some kdevelop self-induced configuration bug because on clean account of the same machine, everything works well:
- importing the same CMake project results with all CMake targets being properly discovered and shown in "Projects" window.
Comment 4 Maciej Mrozowski 2017-12-27 19:56:00 UTC
Other viable workaround is to create new session.
Comment 5 Justin Zobel 2022-11-10 22:32:31 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 2022-11-25 05:20:40 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 2022-12-10 05:17:22 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!