René J.V. Bertin
2016-05-13 13:54:33 UTC
Hi,
With KDevelop 4.7, one could select a project's subdirectory containing a Makefile (as shown by the folder icon), issue a "Build" via the keyboard shortcut or context menu, and KDevelop would issue a make command in the selected directory.
That seems no longer the case with KDevelop 5, and I find that a pity. Was this by popular request? It would seem to me that the "Build Selection" menu should still build only what's selected (if that selection corresponds to a build unit), and that it would be perfectly possible to add dedicated commands for "build whole project".
I know one can select and build one of the build targets, but that's become less useful for big projects you don't know intimately. KDevelop 4.7 could expand those targets to show which files it depended on (so you could see which target to build after modifying a given file), but that feature has gone with the dodo too.
Thoughts?
R.
With KDevelop 4.7, one could select a project's subdirectory containing a Makefile (as shown by the folder icon), issue a "Build" via the keyboard shortcut or context menu, and KDevelop would issue a make command in the selected directory.
That seems no longer the case with KDevelop 5, and I find that a pity. Was this by popular request? It would seem to me that the "Build Selection" menu should still build only what's selected (if that selection corresponds to a build unit), and that it would be perfectly possible to add dedicated commands for "build whole project".
I know one can select and build one of the build targets, but that's become less useful for big projects you don't know intimately. KDevelop 4.7 could expand those targets to show which files it depended on (so you could see which target to build after modifying a given file), but that feature has gone with the dodo too.
Thoughts?
R.