KDevelop project file and documentation

[tim-littlefair]

Added a KDevelop project file and documentation of how to open the project after checking a sandbox out.

Unfortunately the instructions are a bit fiddly, but that seems to be KDevelop.

I only just saw your response #28 (comment), after spending half a day working out how to get a working IDE if /plug.kdev4 is in git (but /.kdev4 is in .gitignore). So it sounds like you'd rather jsut add /*.kdev4 to .gitignore as well, but I hope you don't mind me raising the PR to alert IDE lovers (not everyone I know, usually not me either), that it is possible.

[tim-littlefair]

Thinking about it again, I can rework the PR so that plug.kdev4 goes into .gitignore and I update KDevelop.md so that it covers bootsrapping the IDE project without starting from a checked in file. Leave it with me for a while, unless you change your mind and like this as it stands.

[offa]

Reading through the guide I wonder, whether the guide is even necessary. Kdevelop seems to have native support for CMake – however, I have not used the IDE myself.

So I'd expect working with a off the shelf CMake project should be straight forward and a standard task, users are familiar (or at least with existing documentation available).

[tim-littlefair]

Reading through the guide I wonder, whether the guide is even necessary. Kdevelop seems to have native support for CMake – however, I have not used the IDE myself.

So I'd expect working with a off the shelf CMake project should be straight forward and a standard task, users are familiar (or at least with existing documentation available).

I wrote the guide because it took me a fair amount of experimentation (more than an hour probably), to get my sandbox into a working state under KDevelop - but I was starting from zero knowledge of KDevelop (in fact it wasn't the first IDE I tried to set up when I decided that one would help).

For now I think I'll focus on trying to get the LT40S work into a mergeable state, I can come back and look at this later, if there are potential or actual contributors to the project who might benefit from it at that time. I'll close the pull request, but I won't delete the branch with the current document, and it can be reopened if there is interest.