2011/3/7 Oliver Borm <oli.b...@web.de> > Compilation of OCC works, but pythonOCC aborts after a while. Tested > pythonOCC version 0.4 and 0.5. The 0.5 version breaks already in the > configuration phase: > > Checking OpenCASCADE libraries BinLPlugin not found Missing library > BinLPlugin. Compilation aborted. > > 0.4 version goes a little bit longer, but complains afterwards (sorry > for the german localisation): > > > /var/tmp/portage/dev-python/pythonocc-0.4/work/pythonOCC-0.4/src/wrapper/SWIG/linux_darwin/TopoDS_wrap.cpp:3415:31: > Fehler: TopoDS_Builder3D.hxx: Datei oder Verzeichnis nicht gefunden > > /var/tmp/portage/dev-python/pythonocc-0.4/work/pythonOCC-0.4/src/wrapper/SWIG/linux_darwin/TopoDS_wrap.cpp:3828: > Fehler: Variable oder Feld »TopoDS_Builder3D__kill_pointed« als »void« > deklariert > > /var/tmp/portage/dev-python/pythonocc-0.4/work/pythonOCC-0.4/src/wrapper/SWIG/linux_darwin/TopoDS_wrap.cpp:3828: > Fehler: »TopoDS_Builder3D« wurde in diesem Gültigkeitsbereich nicht > definiert > > /var/tmp/portage/dev-python/pythonocc-0.4/work/pythonOCC-0.4/src/wrapper/SWIG/linux_darwin/TopoDS_wrap.cpp:3828: > Fehler: »self« wurde in diesem Gültigkeitsbereich nicht definiert > > /var/tmp/portage/dev-python/pythonocc-0.4/work/pythonOCC-0.4/src/wrapper/SWIG/linux_darwin/TopoDS_wrap.cpp: > In function »PyObject* _wrap_TopoDS_Builder3D_MakeShell(PyObject*, > PyObject*)«: > > /var/tmp/portage/dev-python/pythonocc-0.4/work/pythonOCC-0.4/src/wrapper/SWIG/linux_darwin/TopoDS_wrap.cpp:17760: > Fehler: »TopoDS_Builder3D« wurde in diesem Gültigkeitsbereich nicht > definiert > > What is the (time)plan of pythonOCC regarding the new OCC version? > > Oliver > > > Hi Oliver,
The pythonOCC SWIG files have to be re-generated from the new release header files, since there might have been changes from 6.3.0 to 6.5.0 in the OCC API. Some other changes are perhaps necessary (for instance remove the BinLPlugin dependency, as you reported). The plan is then as follows: - first manage to get OCC 6.5.0 compiled on MacOSX (I've been playing with it for two hour, and it fails) - just wait for a couple of months to know whether OCC 6.5.0 can actually be trusted. I'm quite sure that, in the following weeks, many messages on the OCC forum will come with patches to the build system (the OCC team did not make any progress with automake) - hack the current pythonOCC so that it becomes compliant with this new OCC release. This part of the work will be a very good opportunity to check the robustness of the wrapper, since it is automatically generated. It took 3 years to generate a wrapper for 6.3.0, I hope it take 3 days to do the same for 6.5.0! Of course any help/feedback is welcome regarding this topic. The next release will also come with the refactored wrapper from Henrik Rustrom, as well as a Sphinx based documentation. Regards, Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
