I have a slight issue with the new CPack stuff.<br><br>CPack.cmake:<br><br>cpack_set_if_not_set(CPACK_NSIS_DISPLAY_NAME "${CPACK_PACKAGE_INSTALL_DIRECTORY}")<br>cpack_set_if_not_set(CPACK_NSIS_PACKAGE_NAME "${CPACK_PACKAGE_INSTALL_DIRECTORY}")<br>
...<br>cpack_set_if_not_set(CPACK_PACKAGE_INSTALL_DIRECTORY<br>
"${CPACK_PACKAGE_NAME} ${CPACK_PACKAGE_VERSION}")<br>
<br>
I set CPACK_PACKAGE_INSTALL_DIRECTORY to:<br><br> set(CPACK_PACKAGE_INSTALL_DIRECTORY "NVIDIA Corporation\\\\OptiX SDK ${CPACK_PACKAGE_VERSION}")<br> set(CPACK_NSIS_DISPLAY_NAME "NVIDIA OptiX ${CPACK_PACKAGE_VERSION}")<br>
<br>In my generated CPackConfig.cmake file I now have:<br><br>SET(CPACK_NSIS_DISPLAY_NAME "NVIDIA OptiX 1.0.0")<br>...<br>SET(CPACK_NSIS_PACKAGE_NAME "NVIDIA Corporation\OptiX SDK 1.0.0")<br>...<br>SET(CPACK_PACKAGE_INSTALL_DIRECTORY "NVIDIA Corporation\\OptiX SDK 1.0.0")<br>
<br>CMake then chokes on the PACKAGE_NAME due to the \O which should be \\O. I set the DISPLAY_NAME and INSTALL_DIRECTORY, but the PACKAGE_NAME is set by the cpack_set_if_not_set and sends my string through an extra processing step.<br>
<br>I can certainly add my own entry for CPACK_NSIS_PACKAGE_NAME to avoid this now that I know about it, but PACKAGE_NAME is a new variable and my old script broke.<br><br>James<br><br><br>