Hi Arthur- I didn't try again with Linux, but slept on the problem, and figured out that my active python installation on os x was looking in the wrong directory. I added a symlink to the correct directory as a hint for macports users. I'm working on condensed set of install instructions for the compiled wrappers... will post when done.
Cheers, Drew On Apr 28, 2009, at 11:59 AM, Arthur Magill wrote: > Hi Drew, > > No problem, sort out the PhD stuff and come back when you have some > free > time. The PhD density around here seems pretty high! I finished mine a > couple of years ago (very much fun, but I was also very happy to > finish > it - but enjoy the road). > > Sounds like OCC itself is probably there, which is good. I've read a > couple of reports of SCons not being too happy under Debian, but > nothing > very reliable. I've tried the SCons install (Fedora 10, i386) and it > worked for me. > > Try Yorik's instructions (sounds like we need to update the wiki). Oh > yes - what version of OCC do you have? Did you manually build yourself > or did you apt-get (I think that will find v6.2.?, you need v6.3)? > > A > > BTW - you're not the only python newbie - I've been meaning to give > it a > try for ages - this library was the final push :-) So far I've written > probably <100 lines > > Andrew Wagner wrote: >> Hi Arthur! >> >> Thanks a lot for your offer to help! I'm preparing for my Ph.D. >> prelim, so it might be a few weeks until I get a chance to get back >> to >> my hobbies. OpenCascade installed without throwing any errors or >> warnings on both mac os x and debian. >> >> cat /etc/debian_version returns 5.0.1 >> >> The SConstruct script seems rather confused: >> >> "Checking whether C++ compiler "gcc" works... no" >> >> gcc is not a C++ compiler; g++ is, and it is most certainly installed >> on my system. I looked through the SConstruct script, and it seems >> like there's an awful lot of very basic platform specific stuff coded >> in there; should some of that stuff be handled by scons? I worry >> that >> is a modern equivalent of a Makefile with a single target consisting >> of a huge shell script. Take everything I say with a grain of salt >> though; I'm still new do Debian, Python, and scons. >> >> Cheers, >> Drew >> >> On Apr 27, 2009, at 5:31 AM, Arthur Magill wrote: >> >>> Hi Drew, >>> >>> I had the same thoughts when I first saw the OCC interface! I'm also >>> learning Python, main triggered by this project. >>> >>> I won't be much help for OSX (Jelle's your man), but I might be able >>> to >>> help get you running on Debian. Could you tell us what you've tried? >>> Did >>> OpenCASACDE itself install properly? This is the hardest part - >>> pythonOCC goes quite easily once that is done. Debian splits occ >>> into >>> quite a few different packages - could you list which ones you >>> installed. Maybe you forgot the dev libs? Also, which Debian release >>> are >>> you running (cat /etc/debian_release I think)? >>> >>> With a bit more info I think we can you started (and then add what >>> we >>> figure out to the wiki, to make that a bit more complete). >>> >>> Cheers, >>> >>> Arthur >>> >>> >>> Andrew Wagner wrote: >>>> Hello- >>>> >>>> In my spare time I work on plans for an open hardware digital >>>> keyboard >>>> over at diykeyboard.org. I initially wrote off open cascade >>>> because >>>> the API is intimidatingly large, and I didn't want to do have to >>>> code >>>> C++ in my free time. I ended up starting my design work using a >>>> demo >>>> version of Rhino3D and their scripting engine, which basically a >>>> vbscript wrapper around their API. Anyway, that's far from ideal, >>>> both because I have beefs with vbscript, and also because the >>>> expense >>>> of the software limits my potential user base. Anyhow, over the >>>> last >>>> few months I have started learning Python, and it sounds like >>>> progress >>>> on Python wrappers to open cascade has been extremely quick! Some >>>> time this summer I hope to experiment with porting my key >>>> generation >>>> scripts over to pythonocc using your tools. >>>> >>>> I tried unsuccessfully to get the wrappers built and installed on >>>> os x >>>> and on debian; it seems like your build system is still very much >>>> in >>>> flux. I look forward to trying out your code again next release! >>>> >>>> Cheers, >>>> Drew >>>> >>>> _______________________________________________ >>>> Pythonocc-users mailing list >>>> Pythonocc-users@gna.org >>>> https://mail.gna.org/listinfo/pythonocc-users >>> >>> -- >>> >>> Arthur Magill, PhD >>> RF Engineer >>> >>> Centre d'Imagerie BioMédicale (CIBM) >>> Laboratory for Functional and Metabolic Imaging (LIFMET) >>> Ecole Polytechnique Fédérale de Lausanne (EPFL) >>> Station 6, CH F1 532 (Bâtiment CH), >>> CH-1015 Lausanne, >>> Switzerland >>> >>> tel: +41 21 693 0569 >>> fax: +41 21 693 7960 >>> email: arthur.mag...@epfl.ch >>> >>> _______________________________________________ >>> 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 > > > -- > > Arthur Magill, PhD > RF Engineer > > Centre d'Imagerie BioMédicale (CIBM) > Laboratory for Functional and Metabolic Imaging (LIFMET) > Ecole Polytechnique Fédérale de Lausanne (EPFL) > Station 6, CH F1 532 (Bâtiment CH), > CH-1015 Lausanne, > Switzerland > > tel: +41 21 693 0569 > fax: +41 21 693 7960 > email: arthur.mag...@epfl.ch > > _______________________________________________ > 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
