On 25 Okt., 04:14, Robert Krawitz <[email protected]> wrote: > On Mon, 24 Oct 2011 12:34:46 -0700 (PDT), kfj wrote:
> > I had to deliberately get swig 2.X as well, but it's needed because > > only 2.X can handle the complexity of the wrapped C++ code competently > > (it's really impressive how the objects, their members and methods are > > transported to python and feel there like native python objects - even > > stuff like STL container classes), and I built it from source (which > > was a snap). But I meant it's more a hugin binary distribution > > problem. If people build from source anyway, getting swig 2.X isn't > > much extra effort. But people just downloading readymade hugin > > binaries may not find it 'in the box' yet. > > Agreed -- until distributions ship swig 2.x, they obviously aren't > going to ship the plugin interface. Again I need to clarify: I got swig 2.X because I wrote the plugin interface with it - swig 1.X wasn't powerful enough. Swig generates the python tinterface from a formal specification. To merely use the python interface, swig is not necessary at all. It's only needed if you compile from source, and even then it could be avoided by taking the output swig produces (which is plain C) and compiling that. Since swig is so easy to be had and using the intermediate C code introduces another step which can potentially go wrong, we decided to make the use of swig mandatory for the compilation and have written the cmake routine so that it will depend on swig2 and refuse to operate without it. And I think most Linux distros have a swig2 packet ready, it's only that the default swig packet is still 1.X. The choice to make swig mandatory also guarantees that the interface will reflect the very object/method infrastructure that thecompiling system is set up with. We felt this approach was preferable, though it can at times break older python code which was written for a previous hugin incarnation. Kay -- 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
