Closed roipoussiere closed 4 years ago
Should I use the latest git commit instead of using the latest release?
This seems better, except one failure in unit tests (#345).
No OCC.Core indicates outdated PythonOCC version.
No OCC.Core indicates outdated PythonOCC version.
I used the latest release of the CadQuery fork of pythonocc-core.
What changes are applied to the CadQuery fork of pythonocc-core compared to the upstream?
Can I safely use the upstream instead of the cq fork in order to use the more recent 0.18.2?
The fact is I'm producing a CADquery flatpak and I would like to base it from a release, not from the latest git commit, in order to be sure that the build is reproducible and the app is stable.
Just use the HEAD of the CQ fork. Changes are related to visualization, If you are only interested in CQ (thus not CQ-editor) then upstream is fine.
Ok thanks.
In order to produce a flatpak, I'm trying to install cadquery from sources. This is a long work (it require to install oce, python-occ and other dependencies from sources) but I think I can see the light at the end of the tunnel. :)
I get the same error as #150 when I try to import cadquery, but I prefer to open a new issue as the other one is fixed.
Installed dependencies:
ls /app/lib/python3.7/site-packages/OCC/
Note that
run_tests.py
from python-occ is executed without error.If I understand well,
OCC
module has been renamed toOCC.Core
in the last release (related commit).So why I still don't have OCC.Core in my site-packages? Should I use the latest git commit instead of using the latest release?