Well. Even though I don't own a Mac and have never used Hugin on a Mac, I'd like to give Harry a big thumbs up for maintaining the OSX build all this time. Harry, great job!
Houdoe :) Bart On Saturday, June 30, 2012 6:39:56 PM UTC+2, DaveN wrote: > > Does this mean Hugin for Mac is dead? Nobody else is thanking you and > I don't have the expertise to build it on my own based on what you > describe. > > Dave > > On Jun 27, 9:30 pm, DaveN <tahoedave...@yahoo.com> wrote: > > Thanks Harry for all your work to date. I don't have any Xcode > > experience so I can't pickup where you are leaving off and it sounds > > very complicated. Good luck to you in your future endeavors. I do > > hope someone picks up on the Mac side of things. > > > > Dave > > > > On Jun 25, 11:07 am, Harry van der Wolf <hvdw...@gmail.com> wrote: > > > > > > > > > > > > > > > > > Hi, > > > > > I'm moving away from Mac OS X and back to Linux: I just bought a new > laptop > > > and put it on Ubuntu. I started using Linux in 1993 (when it was > really > > > only a kernel and a gcc predecessor and few curses based programs) > and > > > since 2003 I completely switched to linux apart from video editing. I > > > switched to Mac OSX in 2006 when I was given a macbook and now I > switch > > > back to (Ubuntu) linux. > > > I won't throw my MacBook Pro out of the window as my wife will keep > using > > > it as long as it will function, but I will move away. > > > (Reasons and rant far below in this mail) > > > > > With regard to Hugin: > > > The XCode project has grown to a complex thing to maintain due to more > and > > > more dependencies and Apple's weird gcc/openmp "strategy" . Having > > > maintained it now for 5 years for me most changes seem like small > steps, > > > unless some GSOC "chunk" moves in. For a newcomer I assume it's > > > overwhelming. > > > > > What I will do in the coming time in the XCode project (next to trying > to > > > keep up with the current developments): > > > - Move from wxwidgets Carbon to wxwidgets Cocoa as carbon is going to > be > > > abandoned and it isn 64bit anyway. This is already implemented in the > > > gui-overhaul branch be it experiemental. > > > - Create several targets: > > > -- a simple non-openmp target group which will build Hugin and > which > > > should be the most simple approach for a starting builder > > > -- a openmp target group for the more experienced, daring builder > (patch > > > here, patch there, patch everywhere). > > > -- trying to build a python enabled target. > > > - Build a scripted portable Hugin bundle from the command line. > > > > > *But the most important line in this email:* In a very near future I > will > > > ask others to step in as builders. > > > Feel free to volunteer now :) > > > > > One more "with regard to Hugin": Lately more and more dependencies > crept > > > in. Next to that: Due to Apple's own curious strategy with regard to > > > apple-gcc support and development, the openMP stuff really becomes a > > > "patched" thing and hard to maintain over OS X versions (think of the > > > enblend issues on Lion, which is now solved fortunately). Non openmp > stuff > > > needs to be compiled with gcc 4.2 or gcc 4.3 and openmp stuff can only > be > > > compiled with gcc 4.6.x (and not officially from Apple) to be able to > run > > > on Lion and up: This Lion OpenMP issue is an open bug for over a year > now > > > and still not solved by Apple and it can only be "solved" with the > > > non-official patched 4.6 gcc. Probably it's "Apple strategy" to do > nothing > > > in this case: They want you to develop on Lion (buy it) for Lion (end > > > users buy it). This patched non-apple gcc 4.6 fails to compile over > 90% of > > > the non-openmp stuff on non-Lion systems. > > > > > === > > > Below you will find my reasons for switching back to linux, which you > may > > > skip completely as it is not really relevant for the main reason of > this > > > mail: requesting new builders. > > > > > Main reason: Video editing is for me the most important part. That > doesn't > > > mean that it is what I use my macbook most for. > > > > > The hardware: > > > I can afford a MacBook pro, that's not the issue. I simply don't want > to > > > anymore. The cheapest 15" MacBrook Pro costs 1750 Euros. A comparable > > > notebook w.r.t. perfomance (and performance only) costs 750-900 Euros: > That > > > notebook misses the Apple MacbookPro superthin, slick design which > actually > > > makes the Apple MBP noisier (or more often noisy) as it can't > dissipate > > > it's heat well enough compared to an "ugly ventilation slides" covered > > > laptop, not all pc notebook have the phantastic discrete video card a > > > MacBook pro has, a pc laptop misses builtin bluetooth (mostly) and it > has a > > > (slightly) inferior keyboard and slightly inferior display. Also: The > > > cheaper notebooks come with more memory and bigger harddisks and some > of > > > them have a discrete graphics card as well be it not as superb as > Apple's. > > > So with Apple: yes, you get very good quality (business ruggedness > instead > > > of consumer plastic) and yes, you pay more for it then necessary. > > > > > About the software, or in other words: which programs do I use: > > > Apple mail, Firefox (Chrome not anymore due it's abuse of personal > data-> > > > use Iron instead), iMovie, VLC, iPhoto, Hugin, ImageFuser, iTunes, > > > ChickenoftheVNC/TightVnc, Teamviewer, Spotlight, Gimp, Audacity, > > > Virtualbox, LibreOffice, ClamAv (to scan the windows stuff from my > > > children), FileZilla, mediainfo, Avidemux, Handbrake, Freemind, > > > RouteConverter and lots of shell scripts. > > > > > Of these programs only apple mail, iMovie, iPhoto, iTunes, ImageFuser > and > > > Spotlight are "real" Apple programs (and ImageFuser is of my own > hand). Any > > > mail program will do (I mostly use gmail from firefox anyway) and I > > > actually don't even like iTunes. > > > In 2009 my previous macbook's motherboard got "toasted" by an external > hard > > > disk (which I had used numerous times) and I switched to linux again > to try > > > it out. After about 6 weeks I bought a (fairly new second hand) > macbook pro > > > as I really missed iMovie (and my son received the laptop restaged > with > > > windows). At that time linux had Kdenlive as most advanced NLE video > editor > > > (next to Cinelerra) but it was very unstable at that time and missing > > > functionality. > > > Kdenlive has evolved and now there is OpenShot as well, which is a > nice > > > combo. Shotwell (started as an iPhoto clone) is really up to standard > now > > > for my needs, and all other programs came/come from linux anyway or > are on > > > linux anyway. > > > What's more: KDenlive now easily outperforms iMovie in functionality. > > > iMovie is very user friendly but (maybe for the same reason) limited > in > > > functionality. > > > > > (And this switches from reason to rant:) > > > What's more: Apple's strategy and way of acting becomes more and more > a > > > nuisance to me. They "close" everything to make it real Apple domains. > Even > > > more than Microsoft they really dictate (really as in dictator) what > is > > > allowed and what not. Coming from the Open Source world and being > really > > > Open Source minded, that really annoys me. No ipod, ipad or iphone for > me > > > as long as Apple moves along this path. > > > > > Hoi, > > > Harry > > > -- > > > Hugin development bundles for Mac OS > > > X< > http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin> > > > ImageFuser for Mac OS X <http://imagefuser.sourceforge.net/> > > > KImageFuser for > > > Linux< > http://panorama.dyndns.org/index.php?lang=en&subject=KImageFuser&text...> -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
