jarvis
jarvis copied to clipboard
Installation on OS X is really hard
Are there any working instructions on getting Jarvis to work on OS X? I tried on Lion and getting all the requirements installed is pretty difficult.
I am still under Snow Leopard. I think you can use macports or brew to install qt & pyqt . The most tricky part is for osg & osgswig. I will try to make each part independant so you can just install a minimal system and then activate each part if you need them.
Yes, osg is installed but osgswig got tricky.
But even for Qt and PyQt you could provide some instructions/directions.
Erik
Sent from my Windows Phone From: madlag Sent: 29.06.2012 11:21 To: Erik Allik Subject: Re: [jarvis] Installation on OS X is really hard (#4) I am still under Snow Leopard. I think you can use macports or brew to install qt & pyqt . The most tricky part is for osg & osgswig. I will try to make each part independant so you can just install a minimal system and then activate each part if you need them.
Reply to this email directly or view it on GitHub: https://github.com/madlag/jarvis/issues/4#issuecomment-6654599
I gave up while trying to install osg, fixed every issue 'brew doctor' gave me and compilation still fails with both stable and development versions. I couldn't get precompiled versions on the osg homepage to work either. Since I won't be using any of the osg related functionality I also vote for separation into modules.
I managed to install osg but osgDB still cannot be imported
Sent from my Windows Phone From: Ozan Sener Sent: 29.06.2012 19:26 To: Erik Allik Subject: Re: [jarvis] Installation on OS X is really hard (#4) I gave up while trying to install osg, fixed every issue 'brew doctor' gave me and compilation still fails with both stable and development versions. I couldn't get precompiled versions on the osg homepage to work either. Since I won't be using any of the osg related functionality I also vote for separation into modules.
Reply to this email directly or view it on GitHub: https://github.com/madlag/jarvis/issues/4#issuecomment-6666477
It would be cool to separate the osg and qt into plugins. While watching the video I was wondering why the qt stuff couldn't be done in an emacs buffer (you were using emacs for other things)
Part of the difficulty with osg on OS X seems to be due to the compiler switch with Lion. At least for me, this tip from #macports worked.
# Clean up stuff
sudo port clean OpenSceneGraph osgswig-devel
sudo port install OpenSceneGraph configure.compiler=llvm-gcc-4.2
sudo port install osgswig-devel configure.compiler=llvm-gcc-4.2
how about homebrew? Installing those 2 ports with MacPorts will also install several dependencies such as python26 which is not really wanted if you already have HomeBrew. Especially if I'm using the Homebrew python with Pymacs.
I'm installing under Ubuntu. And stuck trying to install osg and osgswig. pip install PyOSG
just won't work because of a osgProducer
linking error.
To popular demand, I will separate the different modules, so you don't need osg and even qt, maybe just currse.
Better yet, define and api or protocol and have the modules use it. Witness the emacs version of ipython notebook. Possible because of the api. Then people can scratch their itches...
OSG installed just fine but I struggle with osgswig under Snow Leopard as well.
Any update on this? I too am giving up trying to install on OSX Snow Leopard. Everything else is installed fine but I can't get osgswig working.
I am working on an new version with osg as an option, so you can use all the good parts without the hard ones !
Can't wait! Thanks!
Looking forward to it!