Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2023-01-04 | Clean up licensing metadata | David Robillard | 1 | -0/+3 | |
2022-10-07 | Simplify clang-tidy configuration | David Robillard | 1 | -8/+1 | |
2022-10-07 | Suppress new warnings in clang-tidy 14 | David Robillard | 1 | -0/+1 | |
2022-06-28 | Simplify clang-tidy configuration | David Robillard | 1 | -1/+0 | |
2022-04-23 | Move reserved platform defines from code to build system | David Robillard | 1 | -4/+0 | |
Numerous things warn about this, and it's generally a bad idea to put these in the code since it can result in incompatibly compiled code being linked together. Unfortunately this makes building manually (without the build system) more fiddly, but such is life. | |||||
2022-04-23 | Suppress warnings when building with clang on Windows | David Robillard | 1 | -0/+1 | |
2021-12-17 | Suppress new warnings in clang-tidy 13 | David Robillard | 1 | -1/+2 | |
2021-08-28 | Suppress new clang-tidy warnings | David Robillard | 1 | -0/+2 | |
2021-05-06 | Strengthen clang-tidy warnings | David Robillard | 1 | -2/+0 | |
2021-05-06 | Clean up X11 implementation | David Robillard | 1 | -1/+0 | |
2021-01-02 | Avoid "else" after "return" | David Robillard | 1 | -2/+0 | |
2020-11-22 | Suppress various clang-tidy warnings | David Robillard | 1 | -0/+5 | |
These libc-specific warnings are a new level, even for LLVM. Using an opt-out style for this is probably not going to last. | |||||
2020-11-01 | Run clang-tidy on all headers and fix various issues | David Robillard | 1 | -0/+2 | |
It's a nightmare trying to get this thing to check everything. | |||||
2020-10-30 | Move implementation source files to a conventional src directory | David Robillard | 1 | -0/+12 | |
I think this attempt to be optionally header-only was misguided, particularly installing source code to the system include path. Typically anyone vendoring code just includes the repository and builds from there anyway. This commit moves all the implementation code to a typical src directory (Don't Be Weird). I still think there is some value in simple "inline" deployment, but that would be better achieved another way, like producing a single-file amalgamation that builds anywhere, ala sqlite. |