This gives user control over which folder header should be installed to instead of using hardcoded value include/. Variable CMAKE_INSTALL_INCLUDEDIR is provided after a call to include(GNUInstallDirs)
More info can be found about usage in docs: https://cmake.org/cmake/help/latest/command/install.html
This PR basically replace all $<INSTALL_INTERFACE:include> with $<INSTALL_INTERFACE:include>.
This gives user control over which folder header should be installed to instead of using hardcoded value
include/
. VariableCMAKE_INSTALL_INCLUDEDIR
is provided after a call toinclude(GNUInstallDirs)
More info can be found about usage in docs: https://cmake.org/cmake/help/latest/command/install.htmlThis PR basically replace all
$<INSTALL_INTERFACE:include>
with$<INSTALL_INTERFACE:include>
.It was already correctly used here: https://github.com/HowardHinnant/date/blob/22ceabf205d8d678710a43154da5a06b701c5830/CMakeLists.txt#L173 here: https://github.com/HowardHinnant/date/blob/22ceabf205d8d678710a43154da5a06b701c5830/CMakeLists.txt#L178 and here: https://github.com/HowardHinnant/date/blob/22ceabf205d8d678710a43154da5a06b701c5830/CMakeLists.txt#L184
This fix a bug if user provide
-DCMAKE_INSTALL_INCLUDEDIR=customfolder
, right now generatedCMake/dateTargets.cmake
output a file with:With this PR, generated file will be: