Bug 449793 - switching project build type changes current launch config
Summary: switching project build type changes current launch config
Status: RESOLVED DUPLICATE of bug 429859
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: 5.7.211201
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-08 15:33 UTC by JATothrim
Modified: 2022-02-09 08:48 UTC (History)
2 users (show)

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 JATothrim 2022-02-08 15:33:52 UTC
With CMake project Kdevelop doesn't keep the launch configuration selection same if I switch project build type.
I frequently switch between Debug/RelWithDebugInfo build types and current behaviour is driving me paranoid, since the Kdevelop will often launch the wrong thing if don't re-do the selection after the build type switch.

STEPS TO REPRODUCE
1.  Make CMake project with Debug and RelWithDebug CMake build types.
2.  Add at least two launch configurations in "Run/Configure launches" and then *explicitly* select to last one.
3.  Change CMake build type in "Project/Open Configuration"

OBSERVED RESULT
The selected launch configuration changes after CMake build type changes.

EXPECTED RESULT
The selected launch configuration is kept the same after CMake build type changed.

SOFTWARE/OS VERSIONS
Windows:  none
macOS:  none
Linux/KDE Plasma: Arch Linux 5.15.13 with Cinnamon desktop
KDE Plasma Version: none
KDE Frameworks Version: Version 5.90.0
Qt Version: Version 5.15.2 (built against 5.15.2)

ADDITIONAL INFORMATION
Comment 1 JATothrim 2022-02-08 15:51:08 UTC
Sorry if this is duplicate report. I found following related bug, after I reported this:
https://bugs.kde.org/show_bug.cgi?id=429859
Comment 2 Igor Kushnir 2022-02-09 08:48:08 UTC
Yes, this is a duplicate. Already fixed in KDevelop master.

*** This bug has been marked as a duplicate of bug 429859 ***