-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add include paths with capitalised paths #46
Comments
would "camelcase" forwarding headers be ok? |
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. #include <KDBindings/Signal.h> Probably best implemented using forwarding headers as @winterz noted. I'd stick with the |
In KDUtils, KDGpu we have
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. |
@seanharmer So the point is to only have the |
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.
The text was updated successfully, but these errors were encountered: