Add include paths with capitalised paths

[seanharmer]

It would be nice to be able to do:

#include <KDBindings/signal.h>

on systems with case-sensitive filesystems so that it matches the other KD libraries that we have.

[winterz]

would "camelcase" forwarding headers be ok? i.e #include <KDBindings/ClassName>

[LeonMatthesKDAB]

If the goal is to conform to what the other KD libraries are doing, we should stick to whatever header naming scheme is used there most often. From a cursory glance at KDDockWidgets, KDReports and KDChart, the general style we'd want to mimic is:

#include <KDBindings/Signal.h>

Probably best implemented using forwarding headers as @winterz noted.

I'd stick with the .h file ending though. It's not all that common to leave this out, unless we want to mimic the standard library style...

[seanharmer]

In KDUtils, KDGpu we have

#include <KDGpu/command_recorder.h>

for example. So camel cased lib name (to match the cmake target) and snake case header name with .h suffix mainly to make it easier to read.

[LeonMatthesKDAB]

@seanharmer So the point is to only have the KDBindings folder name be capitalized? Not the individual files themselves?