Hi Kay, I have been a litle distracted the past weeks. I have a new Android tablet and to be able to tune it to my wishes I started creating rooted custom roms (as there wasn't any for my device) and already released a few (others like them as well). Currently, I'm rather satisfied so other topics get renewed attention.
2011/2/7 kfj <[email protected]> > Hi all! > > As you may have gleaned from the traffic on this list recently, work > has been done on the python scripting and plugin interface for hugin. > There is a branch for this project, called python_scripting, and the > python interface and the plugin interface have been made to run on > Kubuntu and Windows. So far, there hasn't been any echo from the Mac > side of things. What would be required is a trial build of the > python_scripting branch under Mac OS, to see if it compiles and runs > there as well. Trying this should require some, but not excessive > effort: > > - The system has to have Python - I don't know what the Mac standard > is, but I'd even think it possible Macs already have it per default. > > Snow Leopard comes standard with python 2.3, 2.4, 2.5 and 2.6 where it defaults to 2.6. You can set the default python selection with python_select . > - The system should have SWIG, the 'Simplified Wrapper and Interface > Generator', version 2.0.1, which should be compiled from source. > > Swig 2.0.1 is part of MacPorts and so is swig-python and can be easily compiled from macports. If compiled from macports the macports version of python will be installed which takes over from Apples python. No problem at all. Python for macports ican be selected from s 2.3-2.7 + 3.2. As python 2.6 is mentioned as prerequisite it would require on OSX (extremely short howto): - install macports from macports.org in terminal: sudo port install python26 sudo port install python-swig (this will automatically install swig 2.0.1 as dependency) sudo port install hugin-app (this will install hugin 2010.4 and all it's dependencies). sudo port deactivate hugin-app (this is a sort of "make uninstall" step. It will remove hugin from it's installation folders, but leave all dependencies intact). sudo port deactivate libpano13 (this will also remove libpano from it's installation paths - somehow get and compile panotools 2.9.18 on your system. Use the default /usr/local install - compile hugin with python extension as described in Kay's link mentioned below, also to the default /usr/local Later on, you can remove the panotools 2.9.18 and huginpython from /usr/local if you want your "clean" system back. > after that it should be a matter of running an ordinary cmake cycle on > the python_scripting branch with BUILD_HSI=ON; the cmake code should > deal with the system-specific details. What's missing from the cmake > code is install targets, since neither T. Modes nor I knew where to > install the Python modules on Mac OS. > > As swig is part of macports, the easy install would be via macports. The install target will also be the macports repository which is /opt/local and which will be automatically taken care off. The install target for the python things will be /opt/local as well. I have some fears with regard to the bundle integration. Otherwise installing to /user/local is no problem either as the several environment settings will take care of that. > So it should be easy - theoretically - but if problems ocur, it'd be > great to know of them now rather than after putting more work into the > code on the platforms it runs on. If any of you have already managed > to compile the branch on Mac OS, please report as well! > > If you want to just read up on the project and don't have access to > the code, the README is also available by itself from my bazaar repo, > and it should give you an idea about what's required to get going: > > http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/README.hsi<http://bazaar.launchpad.net/%7Ekfj/+junk/script/view/head:/main/README.hsi> > > Kay > > This mail is more or less meant as an "info" mail to you and others. I will try to compile it and report back as soon as possible. The current trunk is based on panotools 2.9.18 which is at this moment in a normal cmake environment a complexing factor (see above) as 2.9.17 is the default now on macports (I took care of that myself as it is neccessary for Hugin 2010.4). I have to twist my system a little. I'll be back. Harry -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
