View Issue Details

IDProjectCategoryView StatusLast Update
0032808Open CASCADEOCCT:Configurationpublic2022-01-28 10:40
Reporteraml Assigned Tobugmaster  
PrioritynormalSeverityminor 
Status newResolutionopen 
Product Version7.6.0 
Target Version7.7.0 
Summary0032808: Configuration, CMake - cmake installs custom.sh during configuration step
DescriptionConfiguring step should be responsible for configuration only, no actual installation should be during it. Imagine the following scenario:
1. build and install OCCT to the default folder ( usr/lib for example)
2. when you want to update OCCT, you start configuring.
3. before you install a new version the currently installed version is broken.

Around line 980:

# change custom.bat/sh
if (EXISTS "${INSTALL_DIR}/${INSTALL_DIR_SCRIPT}/custom.${SCRIPT_EXT}")
  file (READ "${INSTALL_DIR}/${INSTALL_DIR_SCRIPT}/custom.${SCRIPT_EXT}" CUSTOM_CONTENT)

  set (CUSTOM_CONTENT "${CUSTOM_CONTENT} ${ADDITIONAL_CUSTOM_CONTENT}")

  file (WRITE "${INSTALL_DIR}/${INSTALL_DIR_SCRIPT}/custom.${SCRIPT_EXT}" "${CUSTOM_CONTENT}")
else()
  OCCT_CONFIGURE_AND_INSTALL ("adm/templates/custom.${SCRIPT_EXT}.main" "custom.${SCRIPT_EXT}" "custom.${SCRIPT_EXT}" "${INSTALL_DIR_SCRIPT}")
endif()
TagsNo tags attached.
Test case number

Relationships

related to 0028153 newinv Configuration, CMake - the "custom" script isn't created in a build dir if it exists in an install dir 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2022-01-28 10:40 aml New Issue
2022-01-28 10:40 aml Assigned To => bugmaster
2022-01-28 10:40 aml Relationship added related to 0028153