Hi All,

Nice work indeed - we must be very close to another release. All the samples 
work just fine here (Fedora 10, i386).

Marco, how far have you got? With the current revision (149) I only have to 
edit 
environment.py (setting OCC_INC and OCC_LIB), then run "setup.py build", 
"setup.py install" and I'm done. I then need to pick up the OCC environment 
variables. I have edited "$CASROOT/env_DRAW.ksh" to reflect my system. I also 
changed it from ksh to bash (by changing the first line) as it isn't doing 
anything clever and I didn't have ksh installed. It now looks like this:

#!/bin/bash

if [ -z "PATH" ];
then PATH=$CASROOT/bin;
else PATH=$CASROOT/bin:$PATH;
fi
export PATH
if [ -z "LD_LIBRARY_PATH" ];
then LD_LIBRARY_PATH=$CASROOT/lib;
else LD_LIBRARY_PATH=$CASROOT/lib:$LD_LIBRARY_PATH;
fi
echo 1
export LD_LIBRARY_PATH
export CSF_MDTVFontDirectory=$CASROOT/src/FontMFT
export CSF_LANGUAGE=us
export MMGT_CLEAR=1
export CSF_EXCEPTION_PROMPT=1
export CSF_SHMessage=$CASROOT/src/SHMessage
export CSF_MDTVTexturesDirectory=$CASROOT/src/Textures
export CSF_XSMessage=$CASROOT/src/XSMessage
export CSF_StandardDefaults=$CASROOT/src/StdResource
export CSF_PluginDefaults=$CASROOT/src/StdResource
export CSF_XCAFDefaults=$CASROOT/src/StdResource
export CSF_StandardLiteDefaults=$CASROOT/src/StdResource
export CSF_GraphicShr=$CASROOT/lib/libTKOpenGl.so
export CSF_UnitsLexicon=$CASROOT/src/UnitsAPI/Lexi_Expr.dat
export CSF_UnitsDefinition=$CASROOT/src/UnitsAPI/Units.dat
export CSF_IGESDefaults=$CASROOT/src/XSTEPResource
export CSF_STEPDefaults=$CASROOT/src/XSTEPResource
export CSF_XmlOcafResource=$CASROOT/src/XmlOcafResource

export TCLLIBPATH=/usr/lib

export ITK_LIBRARY=/usr/lib
export ITCL_LIBRARY=/usr/lib
if [ -n "TIX_LIBRARY" ];
then TIX_LIBRARY="";
fi
export TIX_LIBRARY
export TK_LIBRARY=/usr/lib
export TCL_LIBRARY=/usr/lib

If you still can;t get things running, post the error messages here and I'm 
sure 
we can fix it :-)

Arthur

M. Nawijn wrote:
> Nice work! Besides being "sexy" it also gives a better and clearer
> presentation when shapes becomes more complex. I hope to show a
> complex example in the near future (if I ever get pythonOCC compiled
> on my Fedora box. This still keeps hunting me. Frustrating to see that
> it compiles without a problem at a SUSE installation. Of course I am
> very happy for you :).
> 
> Marco
> 
> 2009/3/18 Thomas Paviot <thomas.pav...@free.fr>:
>> Dear all,
>>
>> I just added a few other samples releated to 'topology building'. I use now
>> another way to develop samples: I base my work on the OpenCascade MFC
>> samples, get the C++ source code generated in a text window, copy/paste and
>> port it to pythonocc. Beware to the Sandor Racz's pythonCascade samples:
>> they were developed with an old release of OCC (5.x), and the 6.3.0 API
>> changed a bit since this release.
>>
>> On the screenshot below (edge.py sample), you can notice that every shape is
>> displayed in different colors: I added a "DisplayColoredShape" in the
>> OCCViewer.py module: I was fed up with the default yellow color. Very simple
>> to use:
>> display.DisplayColoredShape(your_shape, 'RED') (I built a dict with string
>> keys that avoid to import the Quantity module and use Quantity_NOC_RED_NOC.
>>
>> Cheers,
>>
>> Thomas
>>
>>
>>
>> _______________________________________________
>> Pythonocc-users mailing list
>> Pythonocc-users@gna.org
>> https://mail.gna.org/listinfo/pythonocc-users
>>
>>
> 
> _______________________________________________
> Pythonocc-users mailing list
> Pythonocc-users@gna.org
> https://mail.gna.org/listinfo/pythonocc-users


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

Reply via email to