Codespell report for "CMake" (on fossies.org)
The FOSS server fossies.org - supporting "CMake" for many years - offers among others a feature "Source code misspelling reports". Such reports are normally only generated on request, but as Fossies administrator I have just created for testing purposes such a codespell based analysis for the CMake release 3.17.3:
https://fossies.org/linux/misc/cmake/codespell.html
That version-independent (not linked) URL should redirect always to the last report (if available).
Although after a first review some obviously wrong matches ("False Positives" = FPs) are already filtered out (ignored) please inform me if you find more of them so that I can force a new improved check if applicable.
Just for information there are also three supplemental pages showing some used "codespell" configuration details, all obvious False Positives and an misspelling history (log).
Ok, most of the errors are "only" in comments and are therefore not directly visible or relevant for users, but some are found also in output strings or even in the source code itself (that case is marked in the report often by a "?" since the displayed context type wasn't determined).
By the way, as C-layman I wasn't sure whether "langugae" -> "language" at line 46 in the file Source/cmGhsMultiTargetGenerator.h and "emmitted" -> "emitted" at line 256 in the file Source/cmComputeLinkDepends.cxx (and 6 lines below) were really misspellings or should be classified as false positives.
A similar report is available for the current release candidate 3.18.0-rc2 (but only til the next release).
Perhaps more meaningful may be the continuously (!) updated report for the CMake GitLab "master" version which is available within a special restricted "test" folder that isn't really integrated into the standard Fossies services and should also not be accessible to search engines:
https://fossies.org/linux/test/cmake-master.tar.gz/codespell.html
That version independent URL hopefully always redirects to the report for the latest "master" version identified by the short commit ID and a year-month-day string (YYMMDD) representing the according git pull date (mostly = commit date). The refresh rate is currently half-hourly.
Although the correction of misspellings and typos has probably not a top priority, I hope that the report can nevertheless be a little bit useful.