Hi, There was a mistake in the first part of the PAF tutorial. I updated the wiki.
Regards, Thomas 2009/9/18 Thomas Paviot <tpav...@gmail.com> > 2009/9/18 Simon Loic <simon1l...@gmail.com> > >> Hi Thomas, >> > > Hi Loïc, > > >> You're a life saver ;-) >> Seriously, after your commit, I still had the casting error, but after >> switching to swig 1.3.39 (instead of 1.3.36), the error disappeared. Then >> the build step and install went well. >> I have a few remaining questions, if you don't mind. >> >> The two first refer to the install wiki page : >> http://www.pythonocc.org/wiki/index.php/Installing_pythonOCC_on_Linux-- >> --What is the role of : >> source /opt/occ63/env_DRAW.sh >> > > The env_DRAW.sh script contains a set of environment variables that has to > be set up before you can use OCC. You can copy/paste the content of this > file to your .bash_profile. The most important one is the CSF_GraphicShr, > that points to the OCC OpenGL lib, and enables the 3D display. > > > --from which directory should I run >> python >> pythonOCC/Tools/InteractiveViewer/InteractiveViewer.py? >> > > The best way is certainly to launch this python script from the > ./Tools/InteractiveViewer directory. Do you have any difficulty to get it > run? > > >> >> Then, I have some strange errors when following the PAF tutorial when >> setting the parameters p.height and p.radius (see the python.output file). >> And finally I run into a seg fault when calling : >> tutorial_context = >> ParametricModelingContext(p) >> Do you have any idea what is at stake? >> > > Weird, since you followed the instructions available on the PAF tutorial > (from the wiki). Before you go and test PAF, I suggest you shoud first check > that pythonOCC works fine. In the /src/unittest directory, there are 3 sets > of unittests: occ_unittest (test of the basic features), paf_unittest (for > PAF) and topology_unittest (topology/geometry handling). Run each of these > scripts and be sure that they all pass: > python occ_unittest.py > python paf_unittest.py > python topology_unittest.py > > If something is wrong, can you please send back the trace? If everything is > ok, then my tutorial is buggy! > > >> Thanks again. >> >> Loïc >> > > Cheers, > > Thomas > > >> >> PS: I subscribed for the commits ml. >> >> On Fri, Sep 18, 2009 at 1:22 PM, Thomas Paviot <tpav...@gmail.com> wrote: >> >>> >>> >>> 2009/9/18 Thomas Paviot <tpav...@gmail.com> >>> >>> 2009/9/18 Simon Loic <simon1l...@gmail.com> >>>> >>>>> Hi Thomas, >>>>> Thanks for your blameless support. >>>>> >>>>> On Fri, Sep 18, 2009 at 12:12 PM, Thomas Paviot <tpav...@gmail.com>wrote: >>>>> >>>>>> I think it's actually better to compile pythonOCC trunk. It's >>>>>> compliant with the latest rev. of salomegeometry trunk. >>>>>> >>>>>> >>>>> In that case should I use salometrunk instead of the rev.175? >>>>> >>>> >>>> Yes. >>>> >>>> >>>>> >>>>> >>>>>> Maybe you have to add '-march=X86-64 -m64' as an extra compile arg. >>>>>> You can have a look to the environment.py script and copy/paste the way I >>>>>> solved the 64 bits issue on MacOSX. >>>>>> >>>>> >>>>> Actually I've already changed, I changed environment.py : >>>>> ECA = ['-O0','-march=%s'%platform.machine()] to ECA = >>>>> ['-O0','-march=x86-64 -m64'] >>>>> But you could make it conditional in order not to screw 32 bits build. >>>>> >>>> >>>> Absolutely. >>>> >>>> >>>>> >>>>> >>>>>> Strange. What version of swig do you use? Everything goes fine with >>>>>> 1.3.39 but I noticed an error with 1.3.40. I use 1.3.39. >>>>>> >>>>> >>>>> Actually, I use the repositories one which 1.3.36. >>>>> I can give a quick try to 1.3.39, even though you might not see it as a >>>>> good long term solution. >>>>> >>>>> >>>>>> Ok, I will commit in a few minutes what I think is necessary and >>>>>> you'll be able to try it. >>>>>> >>>>> >>>>> I'll try as soon as I see your commit. >>>>> Bye. >>>>> >>>> >>>> Ok. >>>> >>> >>> Change to environment.py commited to svn repository. Please register to >>> pythonocc-commits (https://mail.gna.org/listinfo/pythonocc-commits/ ) ml >>> if you want to be notified about future commits. >>> >>> >>>> >>>> >>>>> Loïc >>>>> >>>>> >>>> >>> 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
