| Summary: | [KDevelop/CMake] : unspecified error message | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | RJVB <rjvbertin> |
| Component: | Build tools: CMake | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jurajoravec |
| Priority: | NOR | ||
| Version First Reported In: | 5.4.2 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | include the project name in the failure dialog | ||
Hello, it is best to send patches the proper way, through Phabricator or Gitlab or they will be lost forever. I did not see this report (with patch) and made my own (maybe worse, who know...) https://invent.kde.org/kde/kdevelop/merge_requests/75 What this actually suggests is that the whole issue tracker here is pointless... There are just too many bugs and reports. Yes, we are probably missing someone to periodically check the new reports and send patches the "correct" way for review... |
Created attachment 123080 [details] include the project name in the failure dialog SUMMARY Version 5.4.x introduced a new error popup when the Cmake projectmanager fails to configure a given project. Problem is, the project isn't identified, which is a bit confusing if you have multiple projects in your session. The attached patch addresses this oversight.