> Hi Niki,
>
>  Thank you for your support.
>
>  In order to build pythonOCC, you need latest version of PY++ and BOOST
>  1.34.1. Compilation fails with BOOST 1.35.0 (I use MSVC 2003 .NET).
>
>  To achieve GCCXML parsing, OpenCascade header files need two minor
>  hacks:
>  * replace the line 27 of Standard_Real.hxx with the following line:
>
>  #if !defined(__PYPLUSPLUS_GENERATION__) && defined(WNT) &&
>  !defined(__CYGWIN32__) && !defined(__MINGW32__)
>
>  * in each .hxx file (more than 15000!), replace #include <xxxx.hxx> with
>  #include "xxxx.hxx". I use the script below (I will upload it to the svn
>  repository).

Thanks for the info.

>  At last, I did not understand the point dealing with  distutils.

Python package installers are 2 types:
 - pure python: containing only *.py sources
 - binary: containing *.py sources and *.pyd extensions

pure installers are compatible with any py2.x runtime and when started
present to users list of available python runtimes for choosing.

OTOH binary installers are compatible with single runtime version only
and have this version as part of filename.

Current installer contains binary extensions but has not info about
that and behaves like pure python package. Usually setup.py for binary
package contains ext_modules= argument and compiles extensions by
itself. As pythonOCC uses external compilation some form of
Extension() unknown to me so far should be used.

regards,
Niki Spahiev

_______________________________________________
Minerva-pythonocc mailing list
Minerva-pythonocc@gna.org
https://mail.gna.org/listinfo/minerva-pythonocc

Reply via email to