CMAKE_PROJECT_NAME: Docs not consistent with behavior
While reviewing !1816 (merged) I noticed that the CMAKE_PROJECT_NAME
docs do not reflect the actual behavior. PROJECT_NAME
gives the name of the most recent project()
call in the current scope, whereas CMAKE_PROJECT_NAME
gives the name of the most recent call in the top most CMakeLists.txt. This behavior seems reasonable, otherwise there's little point having both variables. The same pattern was followed when the DESCRIPTION
keyword was added to the project()
command recently and now it has appeared again in !1816 (merged). Would probably be wise to address this inconsistency before we proceed with !1816 (merged).