View Issue Details

IDProjectCategoryView StatusLast Update
0033565Open CASCADEOCCT:Configurationpublic2024-10-13 12:42
Reporterdrazmyslovich Assigned Tobugmaster  
PrioritynormalSeverityblock 
Status verifiedResolutionfixed 
PlatformWindowsOSVC++ 2022 
Product Version7.8.0 
Target Version7.8.1Fixed in Version7.9.0 
Summary0033565: Configuration - JeMalloc process different build types
DescriptionJemalloc.cmake looks for both static and shared libraries, but only 1 type is required
At the current implementation, jemalloc.cmake is searching for both static library and shared library and requires both of them to be present in jemalloc package. Having only static library or only shared library will fail the whole configuration. At the same time, OCCT requires only 1 library - either static or shared. There is no possibility to control the behavior using CMake variables. Furthermore, having a jemalloc with only static lib or only shared lib will lead to cmake error during OCCT configuration. This makes impossible to use the custom build jemalloc package.
Steps To Reproduce Not applicable
TagsNo tags attached.
Test case numbernone

Activities

dpasukhi

2024-01-02 19:11

administrator   ~0114848

Currently static lib need to use into compiler time.
And shared used to install and use in RealTime.
This kind of package was default for vcpkg and own build process of jemalloc,
JeMalloc do not share own CMake configuration, so, we will create some workaround to process pure static build.
Pure shared build probably not possible to integrate into compiler time.

dpasukhi

2024-10-12 20:32

administrator   ~0116840

https://github.com/Open-Cascade-SAS/OCCT/pull/98

Issue History

Date Modified Username Field Change
2024-01-02 18:47 drazmyslovich New Issue
2024-01-02 18:47 drazmyslovich Assigned To => dpasukhi
2024-01-02 19:08 dpasukhi Status new => assigned
2024-01-02 19:09 dpasukhi Summary jemalloc.cmake looks for both static and shared libraries, but only 1 type is required => Configuration - JeMalloc process different build types
2024-01-02 19:09 dpasukhi Description Updated
2024-01-02 19:11 dpasukhi Note Added: 0114848
2024-10-12 20:32 dpasukhi Status assigned => resolved
2024-10-12 20:32 dpasukhi Steps to Reproduce Updated
2024-10-12 20:32 dpasukhi Note Added: 0116840
2024-10-13 12:41 dpasukhi Assigned To dpasukhi => bugmaster
2024-10-13 12:41 dpasukhi Status resolved => reviewed
2024-10-13 12:42 dpasukhi Status reviewed => verified
2024-10-13 12:42 dpasukhi Resolution open => fixed
2024-10-13 12:42 dpasukhi Test case number => none
2024-10-13 12:42 dpasukhi Fixed in Version => 7.9.0