Hi Thomas, thank you for the answer.
It seems that I expressed myself nor in the right way. I hope I can eliminate missunderstandings.. > > Good, i also use to work with OSX. That is good to hear, I came to the Mac because there I got the most performance for my money for doing simulations (mostly FEM) > > > 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. That is really hard :) On the other hand this shows me that there must be a specific issue with my installation that prevents me from installation like all the other Mac-user. This encourages me to get an other approach in the future. > > Issues related to fink should be reported to the fink ml. I use finkcommander > to manage fink packages: it works quite well. Of course, you are right. It was not PythonOCC related, just my mistake. > > 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... > How does this work for you ? Installation of PyQt and Qt4-x11 via fink builds the libraries with link against the fink-installed python2.6. So the site-packages can´t be executed (imported) from the native Mac Python2.6. So how do you handle this, or am I completely wrong? > 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 read your post about this. I´m not familar with OCC specific relationship between company and open source comunity. > > > 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. In the original post it wasn´t the best wording. I wanted to express that if one of the required libs doesn´t allow a binary distribution due to licence-reasons then there would be a huge limitation also for the software that depends on this lib. I wasn´t aware that a binary distribution is not available just due to timing reasons, what i absolutely understand. I just thougt just a subset is precompiled available, so the rest has a licence that prevents from binary distribution. Sorry, my fault. > > 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 ... I´m glad that you didn´t went fishing ! My remarks were not related to PythonOCC, more likely to QT where it is (at least for me) it is not further possible to download QT4-X11 as source on bin. > > pythonocc is intended to developers, the prerequisite is that you're familiar > with the basic of c/c++/python development. python : yes c++ :no c: no never the less I have build the code for my master-thesis in 1994 in c on a massive parallel infra-structure (does anybody remember the transputer devices ? HPC in the 90th... ). But as far as I´m concerned, this shouldn´t be necessary for using a wrapper under python. Btw, my knowledge in different programming languages didn´t help me.... > > > 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? I propose I´ll ask specialized questions next time I give it a try, ok ? > > > 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. Thank you, is it compiled for the native Mac python ? I assume yes. So I´ll give it a try again This would mean that the binary of PyQT links to the QT-Lib and everything should run under the native python2.6 from SnowLeopard, right ? > > > Sorry everybody, I know it is not your fault, but I´m a little bit p****d ... > > You're welcome, Thank you again, > > > Helmut > > Best Regards, > > Thomas Thomas, I hope I was able to make clear that I don´t want to blame anybody and I really respect the effort you and all the other sw-developer spend. I just was dissappointed. Sorry for the long post, but it was very important for me to correct the wrong imression of my first post. With kind regards Helmut
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
