It's really hard to start developing with KDevelop and Kubuntu 16... On installing the KDevelop package I get a load of errors chucked up about missing project management plugins. Then, I can't save to a directory because KDevelop is too stupid to create a missing directory in the path. Finally, even though g++ and make are installed, KDevelop is too stupid to try and automatically add a C++ compiler, so all the options I have are debug a compiled binary or a plasmoid!!! Visual Studio Community works out of the box; why doesn't KDevelop? If you want to get more contributors to the project - which is something I wanted to do - you need to make it easier TO START DEVELOPMENT!
> On installing the KDevelop package I get a load > of errors chucked up about missing project management plugins. Be more specific please. Maybe Kubuntu's kdevelop package needs to depend on cmake? > Then, I can't save to a directory because KDevelop > is too stupid to create a missing directory in the path. Huh? How do you even navigate the "save as" dialog to a directory which doesn't exist? > Finally, even though g++ and make are installed, > KDevelop is too stupid to try and automatically add > a C++ compiler, so all the options I have are debug > a compiled binary or a plasmoid!!! Wait, is this about building or debugging now? How is debugging related to a C++ compiler? KDevelop doesn't detect compilers, you need your own build system (e.g. cmake) to build your project. That detects the compiler.
Pardon my initial report - it was a little short and a little rude. My apologies. Let me provide you with more data. 1. KDevelop allows me to create a project in a directory that doesn't exist, and then throws an error when trying to save the file it creates. It's easy to replicate this; when the "New From Template" dialog, simply enter a path that doesn't exist in the Location textbox. My (incorrect) assumption would be that KDevelop would create this directory for me - it doesn't. 2. The "missing project management" errors, as well as the missing compiler, were sorted by installing the required CMake plugins. Half user error (me!) and half bad info from KDevelop (could it not clearly state it was missing this?) Thanks! I hope this is useful! Dave
No offense taken. I'll edit the title of the report to the directory issue, since I think that's an actual bug. The cmake error message was reworded for 5.1 a bit already to be a bit more clear what the problem is. Anyways, I think your distribution should simply make KDevelop hard-depend on cmake to avoid this issue for their users, or at least mark it as "recommended" so it is installed by default along with kdevelop if you don't explicitly deselect it.
(In reply to Dave Thompson from comment #2) > 1. KDevelop allows me to create a project in a directory that doesn't exist, > and then throws an error when trying to save the file it creates. It's easy > to replicate this; when the "New From Template" dialog, simply enter a path > that doesn't exist in the Location textbox. My (incorrect) assumption would > be that KDevelop would create this directory for me - it doesn't. Works fine to me with latest git version - I entered unexisting path to "Location" field and path was created during creation of project.
Ok, nice. Thanks for reporting back. If you hit other issues, optimally please open a report for each issue, that makes them easier to track. I'll close this one.