Hi Tom Sorry, but I have to disagree:
On 16.04.2012 22:07, Tom Sharpless wrote: > This thread should be a wake-up call for Hugin's developers. > > If you want Hugin to remain viable on Windows and OSX, you must > discipline your use of packages that assume the Linux "build it > yourself locally" philosophy. The stable Hugin releases have been part of every mature linux distro I know. There is no reason to "build it yourself locally" unless you a) want to live on the bleeding edge of technology and b) your distro does not supply you with nightly builds That is simply not an option for Win > and Mac users, so we have to rely on really heroic efforts by builders > like Harry and Matt Petroff. I agree: Kudos to Harry and Matt for their effort to supply Mac/Win users with recent Hugin versions. I have coded for both platforms and I know how different OSes are and what hurdles you have to jump in order to make IT work. Make life too hard for those guys, and > Hugin becomes a Linux-only sandbox toy. This is the part I can not agree: There are plenty of solutions for creating panoramas for other operating systems than linux/BSD/***ix ... Yes, you will have to pay for those, but you paid for the OS, too, so what? Why should Hugin care for the least common denominator? Where is my CP/M Hugin for my Rainbow 100? Don't get me wrong: I'm not proposing that the Hugin development should abandon mac or windows (or whatever other operating systems one may be porting Hugin to). But neither should the development be restrict to the limitations posed by non ***ix operating systems. Harry is doing it exactly right: he tries to make it happen, getting official OS support or not does not matter. And I'm quite sure that there is a way to get python scripting for windows users, too: After all, TheGimp did it for years, did he not? > I myself stopped building for Windows sometime last year because it > had just gotten too hard to maintain a working build environment -- > and that was before the Python adventure. There are other FOSS projects that have jumped this hurdle, so it is possible to do so. There is no reason to put our collective head into a bucket: there are ways to overcome the limitations imposed upon us by the operating systems. One solution for windows that comes to mind is mingw[1] or mingw-64[2]. Another is cygwin[3] and there is mingw-cross-env [4], too. I have no pointers for MacOS, but given the fact that MacOS is based on some BSD derivate (IIRC), the differences to a ***ix should not be so grave as it is in the win side. > I don't know if it is too > late to reverse this trend, but I do think it would be possible, with > some thought about cross-platform issues, to resolve many of the > current difficulties and prevent many new ones from arising. > Tom, please don't try to stand in the way of the technical advance. You are doing a tremendous amount of work for the development and the support of Hugin and your know-how and expertise in these areas is invaluable. Your concerns regarding the integration of features like the python scripting interface are very valid, but this will drive the development and sooner or later, it will be integrated in the distributions and solved to everyones satisfaction. If not, this egress was an evolutionary death end and we will see a lua/perl/wsh solution sooner or later. With kind regards Stefan Peter [1]http://www.mingw.org/ [2]http://mingw-w64.sourceforge.net/ [3]http://www.cygwin.com/ [4]http://mxe.cc/ > > On Apr 15, 4:12 pm, Harry van der Wolf <[email protected]> wrote: >> Op 15 april 2012 13:10 schreef Stefan Peter <[email protected]> het >> volgende: >> >> >> >> >> >> >> >> >> >>> Hi Harry >> >>> Please forgive my ignorance when it comes to packaging for apple OS, but >>> bundling the complete python stuff with hugin seems at least >>> questionable to me. >> >>> What happens if the users already has a python interpreter installed? >>> Are you aware that you may have to provide (security) updates and >>> support for the python part as well? How many different python flavors >>> and versions may end up on a mac with multiple applications installed >>> that use python if all packagers bundle their own version? >> >>> Shouldn't it be be possible to state something like "If you want to use >>> the python plugins (highly recommended, by the way), please make sure a >>> python package is installed. I recommend ..." in the hugin bundle? >> >>> I'm sure you know that there are official python builds for the mac at >>> http://www.python.org/getit/mac/. >> >>> Just my 2 cents. >> >>> Regards >> >>> Stefan Peter >> >> Thanks for your comments. >> Your arguments are also literally the exact reason for the bundled Hugin >> app as it is delivered now. >> For a "python enabled" Hugin, swig is needed and it needs to be compiled >> versus a python version. Then hugin needs to be compiled against that same >> python and swig version to make it work. And that might work on my system >> but it's not portable to other systems. >> Every OSX comes with it's own python version. Sometimes as ppc/i386, >> sometimes as ppc/i386/x86_64 and lately as i386/x86_64, and between version >> 2.4, 2.5, 2.6 and 2.7. And that's by Apple itself. The same "Apple >> certified" official builds can be downloaded from python.org, like you >> mentioned. These versions are somewhat newer: 2.7.3 and 3.2.3. >> These argument are on the other hand also true for other libraries and >> binaries, which are compiled normally for a certain version and >> architecture, but in this bundle as universal "linked to each other and >> against each other". >> That's exactly why we make the bundles: to make it "stand alone portable" >> apps. >> If I build a python enabled version, it will literally include python and >> swig inside the bundle to make the bundle again a "portable stand alone" >> application like the current bundles, be it without python. >> >> If I can't make that work, we might need to search for another option. >> >> Harry > -- In theory there is no difference between theory and practice. In practice there is. -- 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
