Just ran the code base through cpplint. There’s some overlap but it does do a good job of picking up stuff that needs modernization whereas cppcheck mostly looks for potential problems.
Here’s the log: https://stearnvault.com/wp-content/uploads/2025/02/cpplint.zip
I tried to suppress the style warnings but wasn’t able to suppress the readability/braces warning. At some point, I may run the code base through astyle to help ensure that the style is consistent throughout. 🙂
For the updated directory structure, we can draw inspiration from GNOME: https://gitlab.gnome.org/explore
Their projects aren’t entirely consistent but they’re pretty good about following the best practices used in the open source community
GIMP’s in particular is worth a look: https://gitlab.gnome.org/GNOME/gimp
Down the road, it may be a good idea to look at translation support using something like gettext
