Closed hazelnusse closed 3 years ago
In case it matters, I'm using the following version of cmake:
$ cmake --version
cmake version 3.19.7
Perhaps this is some difference in how CMake handles "." in names? I'm seeing this in build/doc/CMakeCache.txt
:
$ rg "M\.CSS"
CMakeCache.txt
313:FETCHCONTENT_SOURCE_DIR_M.CSS:PATH=
329:FETCHCONTENT_UPDATES_DISCONNECTED_M.CSS:BOOL=OFF
I tried changing MCSS_SOURCE_DIR
to M.CSS_SOURCE_DIR
but it did not fix the problem either.
Adding the following indicates the expected variable names are not getting set:
message("M.CSS_SOURCE_DIR = ${M.CSS_SOURCE_DIR}")
message("M.CSS_BINARY_DIR = ${M.CSS_BINARY_DIR}")
message("M.CSS_ADDED = ${M.CSS_ADDED}")
message("MCSS_SOURCE_DIR = ${MCSS_SOURCE_DIR}")
message("MCSS_BINARY_DIR = ${MCSS_BINARY_DIR}")
message("MCSS_ADDED = ${MCSS_ADDED}")
...
-- CPM: adding package m.css@0 (42d4a9a48f31f5df6e246c948403b54b50574a2a)
M.CSS_SOURCE_DIR =
M.CSS_BINARY_DIR =
M.CSS_ADDED =
MCSS_SOURCE_DIR =
MCSS_BINARY_DIR =
MCSS_ADDED =
I've confirmed that CMake variables names can have dots in them so presumably this must be due to how CPMAddPackage() is parsing the github repository name?
Ehhm yeah this seems to be a bug I introduced in #88, by using the new CPM.cmake syntax. The repository name is now implicitly inferred by the source string "gh:mosra/m.css#42d4a9a48f31f5df6e246c948403b54b50574a2a"
, so it should be ${m.css_SOURCE_DIR}
instead of the previous MCSS_SOURCE_DIR
.
Aha, it is case sensitive. Lol, you beat me! https://github.com/TheLartians/ModernCppStarter/pull/107
On 4212173c2fed1703f1e68a7585c074fa55578be0 when I follow the directions for building the documentation, I get the following:
I have Doxygen, jinja2, and pygments installed:
For some reason, the
MCSS_SOURCE_DIR
is empty and is causing the command of the GenerateDocs custom command to be just/documentation/doxygen.py
.