2010/5/21 Denis Barbier <bou...@gmail.com>

> On 2010/5/21 Thomas Paviot wrote:
> [...]
> > Hi guys,
> > Thanks for your feedbacks with building/installing debian unstable
> > pythonOCC. In order to sum up  your experiments, is there something I
> should
> > add to the README file (which is about to be renamed as INSALL) for
> debian
> > users?
>
> No, README file looks fine, the only problem is that the Debian OCC
> packages do not define any environment variables.  I will send a patch
> in coming days to remove checks against CSF_GraphicShr.
>
> Denis
>
>
I had a discussion a couple of days weeks ago with Olider Borm, who
contributed the debian binary package for pythonOCC-0.4. It seems not
possible to set the CS_GraphicShr variable from the debian packaging tool.
So here is his suggestion:

"""
If there is an automatic way to determine the location of the
libTKOpenGl*.so library if this variable does not exist I would prefer
such a solution. Maybe something like:

ldd /usr/lib64/python2.6/site-packages/OCC/_Geom2dToIGES.so | grep -i
libTKOpenGl
"""

I think it could be a good solution to avoid this annoying step. (Note that
the site-packages directory be known from the sys.modules dict when the OCC
root package is loaded).

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

Reply via email to