Talk:Hugin Compiling Ubuntu

From PanoTools.org Wiki
(Difference between revisions)
Jump to: navigation, search
(autotools: new section)
 
(7 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
== Autopano-sift-C build ==
 +
 +
According to several forums and my own experience on Ubuntu 11.04 you need to install these lib's at first, otherwise, you get errors during building:
 +
 +
<code>
 +
sudo apt-get install libtiff4-dev<br>
 +
sudo apt-get install libpng12-dev<br>
 +
sudo apt-get install libpano13-dev
 +
</code>
 +
 +
Plus, you need to have cmake and mercurial installed.
 +
 +
<code>
 +
sudo apt-get install mercurial<br>
 +
sudo apt-get install cmake
 +
</code>
 +
 +
--[[User:Jerry|Jerry]] 05:44, 27 March 2012 (UTC)
 +
 +
== enblend build ==
 +
 +
I just added the -DCMAKE_INSTALL_PREFIX... to the enblend build instructions. This to make it
 +
easier to find how to change it if you don't want the default. --  [[User:Rew|Rew]] 15:42, 5 February 2011 (UTC)
 +
 +
== older stuff ==
 +
 
In paragraph:
 
In paragraph:
  
Line 14: Line 40:
 
Wouldn't it better to use the same naming convention for hugin, like suggesting to create a build.hugin instead of hugin-build?  
 
Wouldn't it better to use the same naming convention for hugin, like suggesting to create a build.hugin instead of hugin-build?  
 
[[User:Esby|esby]] 22:31, 3 October 2009 (UTC)
 
[[User:Esby|esby]] 22:31, 3 October 2009 (UTC)
 +
 +
Looking through the steps today, I noticed the same sort of thing - in the libpano and enblend steps, the folder structure is libpano.hg and libpano.build (etc.) whereas for hugin we have hugin.hg and hugin.hg-build. Is it okay to rename our build directory for hugin to hugin.build?
 +
--[[User:Onomou|Onomou]] 18:31, 2 May 2011 (UTC)
 +
 +
If you want to rename it, use hugin.hg.build (or libpano-build)  The idea being that the first postfix (.hg) identifies the branch for users who check out multiple branches simultaneously in the same working space (which is what I do when I have an ongoing release or when I am using a development branch.  Libpano does not have active branches (yet).
 +
--[[User:Yuval|Yuval]] 23:49, 17 May 2011 (UTC)
  
 
== Error executing hugin ==
 
== Error executing hugin ==
Line 29: Line 61:
  
 
What am I wrong in? [[User:DonPaolo|donPaolo]] 22:01, 1 January 2010 (UTC)
 
What am I wrong in? [[User:DonPaolo|donPaolo]] 22:01, 1 January 2010 (UTC)
 +
 +
'''Hello,'''
 +
 +
Try to do this:
 +
 +
<code>
 +
$ sudo ldconfig
 +
 +
worked for me, and maybe it could be interesting to add that to the wiki --[[User:Lepuma|Lepuma]] 23:25, 19 October 2010 (UTC)
  
 
== autotools ==
 
== autotools ==
  
 
If autotools is not being used anymore, could we drop it from the compile list?
 
If autotools is not being used anymore, could we drop it from the compile list?

Latest revision as of 07:47, 27 March 2012

Contents

[edit] Autopano-sift-C build

According to several forums and my own experience on Ubuntu 11.04 you need to install these lib's at first, otherwise, you get errors during building:

sudo apt-get install libtiff4-dev
sudo apt-get install libpng12-dev
sudo apt-get install libpano13-dev

Plus, you need to have cmake and mercurial installed.

sudo apt-get install mercurial
sudo apt-get install cmake

--Jerry 05:44, 27 March 2012 (UTC)

[edit] enblend build

I just added the -DCMAKE_INSTALL_PREFIX... to the enblend build instructions. This to make it easier to find how to change it if you don't want the default. -- Rew 15:42, 5 February 2011 (UTC)

[edit] older stuff

In paragraph:

In ubuntu 7.10 AMD64, replace lib64z1 and lib64z1-dev with zlib1g and zlib1g-dev in the above command. COULD SOMEBODY PLEASE DOUBLE-CHECK? You probably meant "In 32bit ubuntu 7.10 systems, ..." And yes, I this works. Heikki 12:10, 4 February 2008 (CET)


This page being about the bleeding edge versioning system installation, it would be useful to note that enfuse adds one more dependency to hugin: exiftools. You need to run sudo apt-get install libimage-exiftool-perl before running it. Personally, I think exiftools is not a good choice for this. Use something that is smaller and more focused to just copying the EXIF data over. Why not use jhead that is already part of hugin distribution? Heikki 12:18, 4 February 2008 (CET)

[edit] Folder naming convention to build

I noticed libpano now uses cmake. cd build.libpano was missing. Fixed it. Wouldn't it better to use the same naming convention for hugin, like suggesting to create a build.hugin instead of hugin-build? esby 22:31, 3 October 2009 (UTC)

Looking through the steps today, I noticed the same sort of thing - in the libpano and enblend steps, the folder structure is libpano.hg and libpano.build (etc.) whereas for hugin we have hugin.hg and hugin.hg-build. Is it okay to rename our build directory for hugin to hugin.build? --Onomou 18:31, 2 May 2011 (UTC)

If you want to rename it, use hugin.hg.build (or libpano-build) The idea being that the first postfix (.hg) identifies the branch for users who check out multiple branches simultaneously in the same working space (which is what I do when I have an ongoing release or when I am using a development branch. Libpano does not have active branches (yet). --Yuval 23:49, 17 May 2011 (UTC)

[edit] Error executing hugin

I'm using ubuntu 9.10, and after compiling and installing hugin, when I try executing it I get:

$ hugin
hugin: error while loading shared libraries: libhuginbase.so.0.0: cannot open shared object file: No such file or directory
$ which hugin
/usr/local/bin/hugin

The deb package installs everything in /usr/local, and libhuginbase.so.0.0 is in /usr/local/lib/.

What am I wrong in? donPaolo 22:01, 1 January 2010 (UTC)

Hello,

Try to do this:

$ sudo ldconfig

worked for me, and maybe it could be interesting to add that to the wiki --Lepuma 23:25, 19 October 2010 (UTC)

[edit] autotools

If autotools is not being used anymore, could we drop it from the compile list?

Personal tools
Namespaces

Variants
Actions
Navigation
tools
Tools