On 2011/3/7 Thomas Paviot wrote:
[...]
> 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.

Hello,

I built OCC 6.5.0 without much trouble on Debian, the situation is
only a little bit worse than 6.3.0 because OCC use outdated
third-party libraries (FreeImage, FTGL).  If you still have trouble
compiling OCC on Mac OSX, you may be interested by our patches (I did
not send them all yet to the OCC forum):
   git clone git://git.debian.org/debian-science/packages/opencascade.git
   cd opencascade
   quilt --quiltrc debian/patches/quiltrc push -a
   cd ros && autoreconf -fi
   mkdir ../builddir && cd ../builddir
   ../ros/configure \
          --enable-shared --disable-debug \
          --with-freetype=/usr --with-ftgl=/usr --with-gl2ps=/usr \
          --with-freeimage=/usr \
          --with-tcl=/usr/lib/tcl8.5 --with-tk=/usr/lib/tk8.5 \
          CPPFLAGS="-I'$(pwd)/inc'"
   make
   make install

You will need to adapt the various --with-* flags above.

Denis

_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users

Reply via email to