2009/9/27 Heath Matlock <heathmatl...@gmail.com>
Hi,

According to your email, and the recent one from Loic, it appears that the
installation of pythonOCC on Linux is not so easy as I thought.

It's been quite a task to install pythonocc this past week. I followed
> both the instructions from these two sites:
>
> http://adl.serveftp.org/dokuwiki/pythonocc


This wiki is not the official one.


>
> http://www.pythonocc.org/wiki/index.php/Installing_pythonOCC_on_Linux
> It was quite a mess trying the scons install, so I'll focus on setup.py
>
> At some point, I created an account for kanzure so he could have a go
> at installing pythonocc on this comp.
>
> Here's the diff -Naur of my subversion checkout setup.py and his:
> http://pastebin.com/f5e093ea8
>
> Here's the diff of the environment.py:
> http://pastebin.com/f283f1c6a
>
>
> I also performed a diff from his subversion and my regular release
> (tar.gz) There is no diff in setup.py from my build copy and kanzure's
> svn, however ther is a diff between the environment.py:
> http://pastebin.com/f1f34f793
>
> from kanzure's dir, build and install runs successfully:
> http://pastebin.com/m3ac8bcb2
>
> However an attempt to launch Interactive Viewer fails:
> http://pastebin.com/m1f3f3338
> Something that might be of note from the above paste is that
> pythonpath shows three diff versions of python being used. This is as
> far as I am able to get on my user account's subversion checkout as
> well, same error occurs.
>
> The attempt to build from my original release dir (using python
> setup.py build -NO_GEOM) has a different error:
> http://pastebin.com/f4b607ded
>
> Here's hoping someone might be able to help me with this.
>

I have a few questions before I can help you:
- what is your platform (Linux I guess, which distribution)?
- is your system 32 or 64 bit?
- which pythonOCC version do you try to build/install? The different diffs
attached to your message are related to a very recent work I commited to the
svn trunk. If you want to install pythonOCC-0.3, just download the archive
available from the website. If you want to build the latest pythonOCC svn
revision, get a local copy of the svn repository. The pythonOCC-0.3 release
doesn't require any additionnal patch (or at least should not).
- the first assumption is that you have a proper installation of
OpenCASCADE. Be sure to have all OCC env variable set up (OCCROOT, CSF_*
etc.).
- the second one is that you have swig-1.3.39 installed. There might be a
few compilation issues if you use another swig  release,
- the best way to compile pythonOCC is then to use setup.py:
python setup.py build
sudo python setup.py install
- 3 different versions of python are installed on your system (2.4, 2.5 and
2.6). It's not a problem. I don't know what is the default version, but you
can install pythonOCC for all of them. For instance, let's assume that 2.5
is the default version, then you can do:
python2.4 setup.py build
sudo python2.4 setup.py install

or

python2.6 setup.py build
sudo python2.6 setup.py install


> Heath Matlock
> +1 256 274 4225
>

Best Regards,

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

Reply via email to