On Thu, Mar 12, 2009 at 11:58 AM, jelle feringa wrote:
>> Yeah, I'm working on it.
>
> you know we appreciate it buddy ;')
Here are some rather unstructured, hairy notes, in more or less rough
order what I had to do to get pythonOCC installed on a copy of debian
on a lab computer. The process was
jelle feringa a écrit :
>
> Yeah, I'm working on it.
>
>
> you know we appreciate it buddy ;')
>
>
> When I was installing it on Windows, python gave me an error at one
> point because comtypes was not installed. So I had to install it in
> order to make it all work.
>
>
> inter
>
> Yeah, I'm working on it.
you know we appreciate it buddy ;')
> When I was installing it on Windows, python gave me an error at one
> point because comtypes was not installed. So I had to install it in
> order to make it all work.
interesting but weird, i wouldnt know what its a dependency
On Thu, Mar 12, 2009 at 9:28 AM, jelle feringa wrote:
> doing something similar for the linuxes would be great.
Yeah, I'm working on it.
> i noticed you mention comtypes on the wiki? i know its useful, but not
> related to
> pythonocc, so i guess its better left
> out.
When I was installing it
its a nice contribution Bryan, thanks.doing something similar for the
linuxes would be great.
i noticed you mention comtypes on the wiki?
i know its useful, but not related to pythonocc, so i guess its better left
out.
-jelle
On Thu, Mar 12, 2009 at 3:23 PM, Thomas Paviot wrote:
> Bryan Bishop a
Bryan Bishop a écrit :
> On Thu, Mar 12, 2009 at 3:37 AM, jelle feringa wrote:
>
>> Would you be willing to sum up getting pythonOCC up & running on the
>> pythonocc.org wiki? There are many paths that lead to Rome it seems so its
>> pretty
>> confusing at some point. It would be great if you
On Thu, Mar 12, 2009 at 3:37 AM, jelle feringa wrote:
> Would you be willing to sum up getting pythonOCC up & running on the
> pythonocc.org wiki? There are many paths that lead to Rome it seems so its
> pretty
> confusing at some point. It would be great if you could consider it,
Way ahead of y
Bryan,
Would you be willing to sum up getting pythonOCC up & running on the
pythonocc.org wiki?
There are many paths that lead to Rome it seems so its pretty confusing at
some point.
It would be great if you could consider it,
Thanks,
-jelle
___
Pythono
Bryan Bishop a écrit :
> On Wed, Mar 11, 2009 at 10:08 AM, Jelle Feringa
> wrote:
>
>> These are the env. vars. relevant to pythonOCC / OCC
>>
>
>
>> export DISPLAY=:0.0
>> export CASROOT=/usr/local/lib/OCC
>>
>
> export CASROOT=/home/bryan/manufacturing/opencascade/OpenCASCADE6.3
On Wed, Mar 11, 2009 at 10:08 AM, Jelle Feringa wrote:
> These are the env. vars. relevant to pythonOCC / OCC
> export DISPLAY=:0.0
> export CASROOT=/usr/local/lib/OCC
export CASROOT=/home/bryan/manufacturing/opencascade/OpenCASCADE6.3.0/ros/
export CSF_GraphicShr=/usr/local/lib/libTKOpenGl.so
p
> Btw, it's supposed to be:
> * export DISPLAY=":0.0"
> (the colon is important, apparently)
I think so.
> Where can I find TKOpenG.so? I tried looking at togl.sf.net,
> downloaded that package and so on, and there's no TKOpenG.so file
> given- there are these though: libToglstub2.0.a, libTogl2.0
On Wed, Mar 11, 2009 at 4:36 AM, Thomas Paviot wrote:
> Bryan Bishop a écrit :
>> It seems I'm missing the OCC.NIS module. When I comment it out in the
>> OCCViewer.py file, InteractiveViewer.py successfully runs-- but the
>> wxWidget interface is not responsive and there are on menu options
>> se
Bryan Bishop a écrit :
> Hey all,
>
Hi Bryan,
> I have some tricks that I've been using. I've got most everything
> nearly working. I have notes available:
>
> http://heybryan.org/books/Manufacturing/pythonocc/scons_notes.txt
> http://heybryan.org/books/Manufacturing/pythonocc/python-setup.py-
13 matches
Mail list logo
