Archived issue #0028153
Configuration, CMake - the "custom" script isn't created in a build dir if it exists in an install dir
Description
custom.sh/bat isn't created if CMake configuration process has found a file with the same name in a further install dir
also CMake config process updates custom.bat (if it exists) in the install dir by adding extra lines and it doesn't check whether these line are already added. The result of this action is a redundant code in the script file
also CMake config process updates custom.bat (if it exists) in the install dir by adding extra lines and it doesn't check whether these line are already added. The result of this action is a redundant code in the script file
Public activity
1 archived note
Participants are labeled by their role within this record.
I observe the opposite situation while building OCCT 7.2.0 with VS 2015 64-bit: custom.bat is not generated in the install folder...
Related records