I don't wish to detract this thread to much from finding a stable build for Mac users but when that task is complete it leaves a burning question: How does the Hugin community prevent such a tragedy in the future?
If there was a way to keep the source up-to-date then building a release binary would not be difficult as there are enough developers out there with XCode. But changing the code of something that a) uses open-gl which has a long history of destroying any sanity one might have had (mainly from graphics card drivers that are near impossible manage; see Lunis's reaction to Nvidia on that point) and b) does math on digital photography which is best left to the realm of PHDs, Adobe employees, and Gods! That diatribe aside, I'd love to see how the Mac specific source code can be kept up-to-date with the Hugin core so binaries can easily be made and mirrors can be uploaded to. Thoughts, ideas? BTW thank you so much for taking it on to make a Mac build of 2016. The old version is almost unusable on El Capitain. and I've yet to get a working linux virtualbox running well enough to manage the intensity needed by a panorama stitcher! On Saturday, April 2, 2016 at 2:45:28 AM UTC-4, Niklas Mischkulnig wrote: > > Why hasn't there been a Mac build on sourceforge for over one year (there > isn't a windows build for the 2016.0.0 yet)? > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/7f12356c-5a26-42a4-8882-6edf07e9cc2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
