Hugin Compiling Fedora

From PanoTools.org Wiki
(Difference between revisions)
Jump to: navigation, search
(add some usage dependencies)
(update to current info)
Line 1: Line 1:
The [[hugin]] and [[enblend]] stable releases are part of default fedora, available via the ''Add/Remove Software'' menu.  Note that there is no [[autopano-sift]] in fedora due to patent issues.
+
The [[hugin]] and [[enblend]] stable releases are part of default fedora, available via the ''Add/Remove Software'' menu.  Note that there is no [[autopano-sift]] in fedora due to patent issues, but [[autopano-sift-C]] can be found in the [http://rpm.livna.org/ livna] 3rd party package repository.
  
Otherwise, recent-ish hugin snapshots and other panorama-related software can usually be found at the [http://bugbear.blackfish.org.uk/~bruno/apt/fedora/linux/ fedora panorama repository].  To subscribe just follow this [http://bugbear.blackfish.org.uk/~bruno/apt/fedora/linux/7/i386/RPMS.panorama/panorama-release-7-1.fc7.noarch.rpm panorama release] link, use the ''Software Installer'' option, and next time you do a ''Software Update'' hugin will be upgraded to the latest snapshot.
+
Otherwise, recent-ish hugin snapshots and other panorama-related software can usually be found at the [http://bugbear.blackfish.org.uk/~bruno/apt/fedora/linux/ fedora panorama repository].  To subscribe just follow this [http://bugbear.postle.net/~bruno/apt/fedora/linux/7/i386/RPMS.panorama/panorama-release-7-1.fc7.noarch.rpm panorama release] link, use the ''Package Installer'' option, and each time you do a ''Software Update'' hugin will be upgraded to the latest snapshot.
  
If you want to compile hugin yourself, just follow the instructions in the '''INSTALL_cmake''' file, you will need these development packages (Jan 2008): libpano13-devel zlib-devel libtiff-devel libjpeg-devel libpng-devel gettext-devel wxGTK-devel boost-devel cmake desktop-file-utils OpenEXR-devel gcc-c++ exiv2-devel
+
If you want to compile hugin yourself, just follow the instructions in the '''INSTALL_cmake''' file, you will need these development packages (June 2008): libpano13-devel zlib-devel libtiff-devel libjpeg-devel libpng-devel gettext-devel wxGTK-devel boost-devel cmake desktop-file-utils OpenEXR-devel gcc-c++ exiv2-devel
  
To also use hugin you may also want [[enblend]], [[autopano-sift]] (or [[autopano-sift-C]]) and perl-Image-ExifTool.
+
To actually use hugin you also need [[enblend]] (>= 3.1) and perl-Image-ExifTool packages.  [[autopano-sift-C]] or [[panomatic]] are useful to automatically generate control points.
  
 
The source RPM package contains an hugin.spec file which is both the build documentation and the script for an automated build (other linux packaging systems work basically the same way).
 
The source RPM package contains an hugin.spec file which is both the build documentation and the script for an automated build (other linux packaging systems work basically the same way).

Revision as of 22:20, 27 June 2008

The hugin and enblend stable releases are part of default fedora, available via the Add/Remove Software menu. Note that there is no autopano-sift in fedora due to patent issues, but autopano-sift-C can be found in the livna 3rd party package repository.

Otherwise, recent-ish hugin snapshots and other panorama-related software can usually be found at the fedora panorama repository. To subscribe just follow this panorama release link, use the Package Installer option, and each time you do a Software Update hugin will be upgraded to the latest snapshot.

If you want to compile hugin yourself, just follow the instructions in the INSTALL_cmake file, you will need these development packages (June 2008): libpano13-devel zlib-devel libtiff-devel libjpeg-devel libpng-devel gettext-devel wxGTK-devel boost-devel cmake desktop-file-utils OpenEXR-devel gcc-c++ exiv2-devel

To actually use hugin you also need enblend (>= 3.1) and perl-Image-ExifTool packages. autopano-sift-C or panomatic are useful to automatically generate control points.

The source RPM package contains an hugin.spec file which is both the build documentation and the script for an automated build (other linux packaging systems work basically the same way).

Personal tools
Namespaces

Variants
Actions
Navigation
tools
Tools