[OSX] Hugin bundle with OpenMP enabled enblend & enfuse

[Harry van der Wolf]

Hi mac users,

This time for the first time a Hugin bundle with an OpenMP(1) enabled version of enblend and enfuse. It's a 32bit version of svn 5102. Until now backward compatibility with Tiger was our (my) most important driver to not use an OpenMP enabled version as OpenMP is only supported on Leopard and Snow Leopard. The entire Hugin bundle itself IS COMPLETELY Tiger compatible but the bundled enblend and enfuse are not anymore.

To support the Tiger users I included a Tiger folder in the dmg containing a Tiger compatible stand-alone enblend and enfuse (read the readme.txt).

OpenMP supports parallel programming which means that parts of enblend and enfuse can use multiple cores on your Mac if you have a multi-core CPU (G5, intel core duo, intel quad-core, etc.)

Please note that with smaller sets that take only a few minutes to stitch the performance gain will not be that big to hardly noticable as the loading of the images takes by far the most time. With big sets the performance gain will be bigger, especially on systems with a lot of memory and on quad core or 8-core systems. 78 12MP images will be about 40-45% faster on duo core and 70-75% faster on quad core. (These numbers are from another user as I don't have multiple macs and my mac is a duo core.)

As always: Information and binaries via my website
<http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>.

(The binaries themselves are served from hugin.panotools.org who kindly provide the disk space and bandwidth).

Hoi,
Harry

(1): http://openmp.org/wp/about-openmp/

[AKS-Gmail-IMAP]

Harry,

This new version crashes on startup. The crash log says libpng.3.dylib is missing.

Allan

--
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 hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[AKS-Gmail-IMAP]

Harry,

The missing libpng.3.dylib message may be one symptom of something else. When looking into the bundle at the Libraries folder, none of the files are symbolic links like one would see in any of the other version bundle Libraries folders.

Allan

On Apr 2, 2010, at 4:47 PM, Harry van der Wolf wrote:

[phar...@gmail.com]

On Sat, Apr 3, 2010 at 5:03 PM, AKS-Gmail-IMAP <akse...@gmail.com> wrote:

> Harry,
> This new version crashes on startup. The crash log says libpng.3.dylib is
> missing.

Well, this new version, 5102, runs just fine here. iMac G5, OS
10.5.4, 2 GB ram.

Steve

[Harry van der Wolf]

Hi Allan,

I don't understand what is going wrong on your system. I downloaded my own bundle and it is perfectly alright on my system. It runs find with all the libraries at the right place with all the symbolic links in place.
Did you "cp" the bundle from the command line?

Harry

2010/4/3 AKS-Gmail-IMAP <akse...@gmail.com>

[AKS-Gmail-IMAP]

Hi Harry,

I expanded the .dmg on one machine (ppc 10.5.8) and copied it to where I normally keep Hugin versions. I then transfered it to another machine (intel 10.5.8) via a thumbdrive. I do not always transfer via thumbdrive but I do frequently use it for this purpose. It was that process that seemed to cook Hugin and all the Libraries files. This is the first time I have ever seen this problem and I'd like to know what happened. I repeated the process for another machine using both the downloaded 5102 dmg and the original defective Hugin that was still on the thumbdrive . The Hugin expanded from the dmg version functioned properly and its Libraries files looked normal (ie many symbolic files). The defective Hugin crashed as before and its Libraries files also appeared as non linking. I image the cause is obvious to you guys as much as it has topped my roof.

Allan   

[Harry van der Wolf]

Hi Allan,

I assume this thumbdrive was formatted as FAT (aka msdos), either as fat-12, fat-16 or fat32. The Fat format doesn't support symbolic (hard and soft) links. So you lose them when copying "something" containing these links to a fat partition. If you put the dmg on the thumbdrive it is just an archive form, like zip or tgz, only that a dmg is an disk image format like ISO. When you expand the dmg to a "link supporting" partition eveything works as it should do.

Harry

2010/4/4 AKS-Gmail-IMAP <akse...@gmail.com>