View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0032808 | Open CASCADE | OCCT:Configuration | public | 2022-01-28 10:40 | 2023-09-29 17:38 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | minor | ||
| Status | new | Resolution | open | ||
| Product Version | 7.6.0 | ||||
| Target Version | Unscheduled | ||||
| Summary | 0032808: Configuration, CMake - cmake installs custom.sh during configuration step | ||||
| Description | Configuring 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() | ||||
| Tags | No tags attached. | ||||
| Test case number | |||||
| related to | 0028153 | new | Configuration, CMake - the "custom" script isn't created in a build dir if it exists in an install dir |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-01-28 10:40 |
|
New Issue | |
| 2022-01-28 10:40 |
|
Assigned To | => bugmaster |
| 2022-01-28 10:40 |
|
Relationship added | related to 0028153 |
| 2022-10-24 10:39 | szy | Target Version | 7.7.0 => 7.8.0 |
| 2023-08-01 15:09 | dpasukhi | Target Version | 7.8.0 => Unscheduled |
| 2023-09-29 17:38 | vglukhik | Assigned To | bugmaster => |
