Hi mac users, Next to the Hugin application itself, the Hugin project comes with quite some command line tools. Within the Hugin application bundle only a few tools are used. These are the tools necessary to make the bundle function: nothing more. In the past we also built "stand-alone" tools, but they have not been updated for a very long time. Also some new tools have been created which have never been built yet for release AFAIK (I'm talking about MacOSX here). The tools mentioned are "command line" tools, not graphic tools with a GUI.
I will first explain the "new approach". (If you are too impatient you can just skip it.) ++ As mentioned: In the past we also built "stand-alone" tools. These tools were statically compiled (for those who know what that means). For some reason I can't compile static tools anymore from XCode. I'm affraid it is some "enhancement" form Apple as Apple has always done it's very best to prevent static builds and to promote dynamic builds. As such this is a very good strategy, but really preventing one from compiling static builds is something else. The static tools were compiled with "everything necessary" compiled into the tool. This had the advantage that you could use the tool without having to think of dependencies. The big disadvantage was that each and every tool was really big, as "everything necessary" came built within every tool. With dynamic tools the "everything necessary" is delivered only once outside the tools, as dynamically compiled libraries. The tools simply use the "everything necessary" dynamically compiled libraries also dynamically. This means of course that the tools need to know where to find these dynamically compiled libraries [0] and that's also the disadvantage of the new package. You need to maintain the "integrity" of the folder structure inside the package. As such this is only a minor problem: just read the Readme.txt ++ The package comes with the following tools: align_image_stack, autooptimiser, calibrate_lens, celeste_standalone, cpclean, deghosting_mask, fulla, hugin_hdrmerge, matchpoint, nona, pano_trafo, pto2mk, tca_correct, vig_optimize, enblend, enfuse, PTblender, PTcrop, PTinfo, PTmasker, PTmender, PToptimizer, PTroller, PTtiff2psd, PTtiffdump, PTuncrop. The hugin tools are from svn 4876 from 11 Jan 2010. The libpano tools (PT*) are from svn 1216 from 10 Jan 2010. Enfuse and Enblend are the version 4.0 binaries. (Anything missing? Let me know). Please note that autopano-sift-c and panomatic are NOT in the Hugin_tools_20100111.dmg due to the license restrictions for the algorithms and their implementations for SIFT (USA) and SURF (USA and Europe). These tools can be obtained via other ways. Please read the Readme.txt inside the Hugin_tools folder in the .dmg on how to "install" and use the tools. The Readme.txt is also attached to this mail (with windows line feeds to make it readable for the entire world ;-) ). The Licenses folder does not need to be copied/installed. It is there to inform you about the licenses involved for the several tools. 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 [0]: compiling/building dynamic libraries and installing them works by default the same as on Unix/Linux/BSD but can be made to work differently. On MacOSX all libraries and binaries have meta-data where to find each library they are compiled against: the install_name_path, which points by default to default paths. This install_name_path can be changed. That's also how the bundle is made. The binaries and libraries (looking for their dependent libraries) are modified to only look inside the bundle at specific locations "for each other". That's also how the tools and libraries are modified within this Hugin_tools folder structure.
Readme.txt for Hugin_tools package version 0.2, 11 January 2010, Harry van der Wolf The tools inside this package are "command line" tools, not graphical tools. == How to "install" this package == - Copy the Hugin_tools directory inside this dmg to a location of your liking. == How to use the tools inside the Hugin_tools directory == 1. Open a terminal 2. cd into the Hugin_tools directory 3. issue the command "source ./set_environment.txt" (without the double quotes) The tools reside inside the bin directory but are system wide available due to the command issued in (3.). The bin directory inside this Hugin_tools directory is set as first entry in your PATH statement. It means that you can execute the tools without needing to use path names. Note: This insertion into your PATH is not a permanent change but only valid in this terminal session. You can also skip the steps 1-3. In that case you need to provide the full path to the relevant tool, e.g. /path/to/folder/Hugin_tools/bin/<tool name>. Note2: due to license restrictions autopano-sift-c and panomatic are not part of this package. =================================================================================================================== License Agreements The programs included in this package are released under the GNU General Public License version 2. If you do not agree with the GPL vs. 2 license agreement, please delete this package and it's contents immediately. This package is completely based on the Hugin project and the tools it contains. Hugin can be downloaded from http://hugin.sourceforge.net. Next to the Hugin tools also enblend, enfuse and the PT* binaries from panotools are included.
-- 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
