Community
Participate
Working Groups
The Build Hammer action builds whatever is currently selected. This is problematic when using references, as say an error is reported in a referenced header. Having fixed the error, the user requests a build, and only the project containing the .h is built, not the top-level project the user was building... I envisage this would work similarly to the LaunchHistory, and there'd be a preference to control whether current selection or last item in history is built.
Created attachment 186847 [details] patch 1 Implementation. Requires CDT builder learns about configurations.
Being used to MS Visual Studio so far (with around 100 subprojects) I would like to have either: - "re-build last project" or rather - introduce some kind of "active project" - run "build active project" In Visual Studio I hit two keys to compile the whole project and to start debugging without fiddling with the mouse in context menus. As a workaround you can select a project in the explorer and invoke "build project". But it is easy to inadvertently select the wrong project, especially when "link with editor" is active.
patchset at: https://github.com/jamesblackburn/cdt/tree/bug/333992_build_history
