Difference between revisions of "Hugin Compiling Fedora"
(→Get a hugin.spec file)
(Add Compiling category)
|Line 97:||Line 97:|
Revision as of 19:11, 11 July 2011
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 RPM Fusion 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. (some redhat/centos packages can also be found at the same location).
If you want to compile hugin yourself, just follow the instructions in the INSTALL_cmake file, you will need these development RPM packages (January 2011):
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 glew-devel freeglut-devel mesa-libGLU-devel libXmu-devel
To actually use hugin you also need make, shared-mime-info, enblend and perl-Image-ExifTool RPM packages. autopano-sift-C or panomatic are optional now that Hugin has a built-in control point generator.
Basic compilation instructions are:
tar -bxvf hugin-2010.4.0.tar.bz2 cd hugin-2010.4.0 mkdir BUILD cd BUILD cmake .. make sudo make install
This will install Hugin and its libraries to /usr/local, this is the preferred location for any software installed without a package manager.
rpm building instructions
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).
First set up your fedora system for building rpms, install some packages (as root):
yum groupinstall "Development Tools" yum install rpmdevtools
Using a normal user account create a build tree, by default this is ~/rpmbuild:
Get a source tarball of hugin
Either download the current stable .tar.gz (or tar.bz2) file from sourceforge or get the latest from Mercurial.
If you have fetched the code via Mercurial you can now create a tarball like so:
mkdir BUILD cd BUILD cmake .. make package_source
('package_source' is a make target, targets are things like 'all' or 'clean' or 'install', this one just creates a tarball)
Get a hugin.spec file
Download an existing hugin .src.rpm file and extract the hugin.spec file by running this command as a normal user:
rpm -ivh hugin-2010.2.0-1.src.rpm
This should put the .spec file where rpmbuild expects to find it.
The next step is to put the .tar.bz2 file where rpmbuild expects to find it:
..and run rpmbuild to create both the SRPM and RPMS at the same time:
rpmbuild -ba ~/rpmbuild/SPECS/hugin.spec
This will fail, probably. You need to edit the .spec file to change the 'Version:' entry to match the number of the tarball, install any missing build dependency rpms, and try again.
Building with mock
'mock' is a more sophisticated system for creating RPMS, it is possible to build multiple architectures and create packages for different releases of fedora and redhat enterprise linux on a single fedora system.
Install mock as root and add yourself to the 'mock' group (use your user name, not 'myusername'):
yum install mock usermod -a -G mock myusername
Follow the instructions above for creating rpms, but just create the source rpm instead:
rpmbuild -bs ~/rpmbuild/SPECS/hugin.spec
Then you can build rpms from this src.rpm with mock like so:
mock -r fedora-11-i386 rebuild ~/rpmbuild/SRPMS/hugin-2009.1.0-0.src.rpm
The first time you do this it will take a very long time while it downloads and assembles a 'virtual' machine, but subsequent builds will only take a few minutes.