GEOM was updated as well. If you don't need GEOM, pass --disable-GEOM to
setup.py. Otherwise, you have to rebuild GEOM located in the contrib folder.
cmake, make and make install.
Thomas
2011/9/30 István Csanády
> Hi,
>
> I am getting the following linker error when I try to bulid the current
>
Hi,
I am getting the following linker error when I try to bulid the current
pythonocc with OCE 0.6.0
Undefined symbols for architecture x86_64:
"GEOM_Object::UnsetMarker()", referenced from:
__wrap_GEOM_Object_UnsetMarker in SGEOM_wrap.o
"GEOM_Object::GetMarkerTexture()", referenced fro
The OCC API changed between 6.3.0 and 6.5.1. As a consequence, pythonocc
SWIG files were updated to be consistent with the new API. You need OCC6.5.1
or OCE-0.6.0 to be able to run pythonocc current master.
Thomas
2011/9/30 István Csanády
> I was going to rebulid pythonocc 0.5 with OCE 0.6.0 to
I was going to rebulid pythonocc 0.5 with OCE 0.6.0 to try to check if the
code I sent does still crash or not with 0.6.0, but it misses BinLPlugin. Do
I have to download the latest pythonocc version to build with OCE?
On Fri, Sep 30, 2011 at 11:13 AM, Thomas Paviot wrote:
> 2011/9/30 D. Barbier
2011/9/30 D. Barbier
> On 2011/9/30 István Csanády wrote:
> > Thanks Thomas, this solved the leaking issue. Any ideas for a workaround
> for
> > the MMGrOpt crash (when I don't remove gcurve.GetObject())? Or I will
> have
> > to wait for pyocc 0.6?
>
> Hello,
>
> Can you please check whether your
Hi Denis,
On Fri, Sep 30, 2011 at 10:59 AM, D. Barbier wrote:
> On 2011/9/30 István Csanády wrote:
> > Thanks Thomas, this solved the leaking issue. Any ideas for a workaround
> for
> > the MMGrOpt crash (when I don't remove gcurve.GetObject())? Or I will
> have
> > to wait for pyocc 0.6?
>
> He
On 2011/9/30 István Csanády wrote:
> Thanks Thomas, this solved the leaking issue. Any ideas for a workaround for
> the MMGrOpt crash (when I don't remove gcurve.GetObject())? Or I will have
> to wait for pyocc 0.6?
Hello,
Can you please check whether your crash happens with OCE 0.6.0? We
fixed
Thanks Thomas, this solved the leaking issue. Any ideas for a workaround for
the MMGrOpt crash (when I don't remove gcurve.GetObject())? Or I will have
to wait for pyocc 0.6?
Last night I have been profiling some pythonocc code and I have noticed that
collect_object is a quite slow even if I remove
