Currently, we provide a patched OCCT conda package in two versions on our conda channel dlr-sc: One for static and one for dynamic linking. We need to provide all static dependencies of OCCT as well. This is quite a maintenance burden. The channel is constantly at its quota limit and currently, we don't have a working CI for MacOS, because I haven't gotten around to fixing the static OCCT and its dependencies for our build chain yet.
Since TiGL works with the non-patched OCCT version in principle, we could consider to do without static linking against OCCT as well. Then we could use the conda-forge maintained OCCT version. If we were to publish tixi3 on conda-forge as well, we would not need any dependencies from dlr-sc at all. Then we could even publish tigl3 on conda-forge and the channel would become obsolete (at least for tigl3 related stuff).
Currently, we provide a patched OCCT conda package in two versions on our conda channel
dlr-sc: One for static and one for dynamic linking. We need to provide all static dependencies of OCCT as well. This is quite a maintenance burden. The channel is constantly at its quota limit and currently, we don't have a working CI for MacOS, because I haven't gotten around to fixing the static OCCT and its dependencies for our build chain yet.Since TiGL works with the non-patched OCCT version in principle, we could consider to do without static linking against OCCT as well. Then we could use the conda-forge maintained OCCT version. If we were to publish tixi3 on conda-forge as well, we would not need any dependencies from dlr-sc at all. Then we could even publish tigl3 on conda-forge and the channel would become obsolete (at least for tigl3 related stuff).