Core build launch configurations are not persistent. about cdt

[ewaterlander]

CDT 10.7.1 still has the problem.

[ewaterlander]

Isn't a launch configuration a strange place to store build configuration settings (besides the fact that they are only in memory, not in the launch file)?
In a managed build project the build configuration settings are stored in the .cproject file.

[mbooth101]

Core build was an initiative to simplify build mechanism especially in the case where the build system took care of most things internally (e.g. Makefile, CMake, Meson). These build systems are things that CDT must "launch", I don't think it's very strange to store configuration for things we must launch in launch configurations.

Documentation is a bit sparse, but here's one of Doug's old slide decks on the off-chance it is helpful: https://wiki.eclipse.org/images/e/e2/CDTCoreBuild2017.pdf

However you certainly found a bug here I think because when I change the build output location, the compiled binary artifact is not detected (there is no binaries container in the project explorer) and cannot be launched (I believe the dynamically created launch configurations rely on being able to detect the built binary artifact in order to avoid any additional user configuration).

[ewaterlander]

I think this bug is related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=552070

[ewaterlander]

The fix for bug 552070 fixed the problem of the settings getting back to default after close and reopen of the project.
See PR #192

The problem that the launch configuration is gone after close project and restart Eclipse is still there.
Fixing this by restarting Eclipse while the project is open does get the proper settings back when the fix for bug 552070 is included.

[ewaterlander]

Although the launch configuration keeps the correct settings after project closure or Eclipse restart, the actual building is not using the correct settings.

Create a Makefile Core Build project. Change Build Output Location to "Build in Project directory". Close and reopen the project, or restart Eclipse. Whatever the setting is for the Build Output Location, the build will always use "Build in configuration specific directory".

[ewaterlander]

The last problem was only present for the Core Build Makefile project Run configuration, not for Debug.
The problem is fixed in PR #314 .