2011/4/20 Helmut Müller <helmut.muel...@ingenieurbuero-mbi.de> > Hi all, >
Hi Helmut, Welcome to this ml, > > I´m new to the list, so best regards to everybody. Sorry for my english, no > native speaker... > > I just tried to install OCC and PythonOCC an a Mac. > Good, i also use to work with OSX. > > It is a PIA ! > > I´m sorry, but I assume that this Installation is nothing for Mac-Users, am > I right ? > Hard to say, but you're the first to report such difficulties. > > You have to install QT4-X11 via fink, as the tar-ball is no longer > available, the installation depends on python that has to be installed via > fink, too. The available python (same version) is ignored. > Build with all dependencies takes half a day. Mentioning that fink per > default compiled 32bit binaries took just a second, building 64bit took the > other half day. > > The next day went away while I tried to compile PyQT-4 from sources. With > the fink installed QT it didn´t work, so I installed this later on via fink, > too. > Issues related to fink should be reported to the fink ml. I use finkcommander to manage fink packages: it works quite well. > > Fiddling around with the different python installations was great. The > installation of the precompiled packages 64bit SL was easy, but > unsuccessful: > The precompiled binaries are built upon the default Mac python (2.6), not the fink one. fink is required only for running the PyQt graphical display. > > the python interpreter is able to import OCC and PyQt4, but when trying one > of the examples: > Fatal Python error: Interpreter not initialized (version mismatch?) > Abort trap > > so, obviously different compilers used for the libs... > > recompilation is not possible, as compilation of PyOCC depends on the > SourceDistribution of OCC, but: 6.3 is no longer available for download > since 6.5 > We're going to move to the latest OCE version as soon as possible. Issues with the OpenCascade distribution should be reported to the OpenCASCADE company. > > I´m aware that I´m a newbie to this software, but I´m very frustrated now. > I did spend 3 hole days for nuts. > It's too much, indeed. > > Why is it not possible to offer an (easy) installable Solution ? I really > like OpenSource, but If it is prohibited to provide working binary downloads > due to restrictions or dependencies, the meaning of "open" is really > missed. Will there ever be a chance just to download this package, install > and try it out ? Not everybody is able to spend days just for compilation, > at least for me, this adventure has to be finished until a solution for the > problem is found. > I think there is a misunderstanding about 'open' source. 'open' actually means that nothing is kept secret in the development process, according to me. Managing different precompiled binaries requires is hard to maintain. I spent hundreds of hour of my spare time to develop free and open source software, several people contributed to the project. You mean I "missed the meaning of open"? I should have go fishing ... pythonocc is intended to developers, the prerequisite is that you're familiar with the basic of c/c++/python development. > I´d really like to hear from one other person how he or she did complete > successful a fresh install of PythonOCC/OCC on MacOS. Any advice is > appreciated. > Sure. BTW, what is your question? > > Btw, why is the download of the precompiled PyQT for SL is no longer > available? Nokia-restrictions ? > No. The link was broken, I uploaded the file to the googlecode page, see http://code.google.com/p/pythonocc/downloads/list. I will update the blog entry related to this topic. > > Sorry everybody, I know it is not your fault, but I´m a little bit p****d > ... > You're welcome, > > Helmut > Best Regards, Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
