Open Durksz opened 2 years ago
Hey @Durksz.
I might have identified the reason behind the sudden rise in file size.
I have started looking into the possibility of splitting up the upstream dependency occt
into different packages with varying number of dependencies. You can follow the progress here -> https://github.com/conda-forge/occt-feedstock/issues/93
If you manage that would be awsome!
Dear Paviot and other developers of Pythonocc-core,
I've been using the Pythonocc-core libary with a lot of enjoyment for the past couple of years. thank you very mucht for the development of the libary!
I've created executables with pythonocc in the past, upto version 7.4 the filesize was managable (around 300-400 mb, big but manageble). I've tried to upgrade to the new 7.6.2 version. but are running into a problem. The new version, installed from the tpaviot repo (or conda-forge) requires multiple libaries, more than the 7.4 version, to be able to install (like the MKL libary among others).
The file size of an executable exeeds now 1 gb, for even a simple program, which is far too much . Sadly I'm not able to compile the source code myself (not smart enought for this).
Is it possible to provide a Pythonocc-core libary version with the bare minimum of dependend packages on conda (or pip)?