Beta 4 was released in February and I think the 'Exposure tab' was
added since then.
Maybe someone has packaged a newer version for Ubuntu? ..or you
could compile from SVN:
http://wiki.panotools.org/Hugin_Compiling_Ubuntu
--
Bruno
<http://wiki.panotools.org/Hugin_Compiling_Ubuntu> building from SVN
should get you there where you want.
if you find inconsistencies/errors in the instructions posted on that
wiki page, please report back.
Yuv
> hugin: error while loading shared libraries: libhuginbase.so.0.0:
>cannot open shared object file: No such file or directory
>The library has been installed to /usr/local/lib
>As I'm not an experienced linux user I don't know how to set up these
>path.
The ultimate solution is to get some .deb snapshot packages
released, as there is no need for everybody to have to jump through
these hoops.
The problem as you discovered is that your system doesn't look for
libraries in /usr/local/lib.
You can get this to work on your system by setting the
LD_LIBRARY_PATH environment variable or by adding the path to
/etc/ld.so.conf
(please somebody correct me if this isn't the right advice for
ubuntu)
--
Bruno
Since I have no problems here with kubuntu, I searched for this reference.
Here it is in "/usr/lib/libglut.so.3", which is a part of "freeglut3"-package.
(This is _not_ freeglut3-dev)
> After "./configure" I found the following warning:
>
> checking for GLUT library... no
> configure: WARNING: WARNING: GL/GLU/GLUT not found, disabling GPU
> mode
>
> I'm finding header files under /usr/include/GL (glut.h,
> freeglut.h ...)
> I'm finding libraries under /usr/lib (libGL.so.1.0.9639, libGLU.so.
> 1.3.070001, libglut.so.3.8.0 and some links to it)
>
> I fiddeled around with installing and uninstalling the packages:
> freeglut3-dev, libglut3-dev and glutg3-dev but was not successful.
> When getting the libraries as described below, both packages freeglut3-
> dev and libglut3-dev are installed.
> sudo apt-get install pkg-config libtiff4-dev libboost-graph-
> dev libboost-thread-dev \
> liblcms1-dev libglew-dev libplot-dev
> libglut3-dev libopenexr-dev libopenexr2c2a
>
> Maybe it shouldn't build "enblend-gpu.o" at all ..?
>
> So I'm quite lost here and can't build enblend under ubuntu.
>
Hope it helps.
Kornel
--
Kornel Benko
Kornel...@berlin.de
I had the same problem on fc8 x86_64 and got it to compile by
starting with a fresh enblend CVS checkout.
Though now I get the same error building in a mock chroot with all
the right headers/libraries installed, so there is something else
going on here.
--
Bruno
Make sure that you have x86_64 libraries installed.
[root@kursk lib]# yum list mesa-libGL mesa-libGLU
Installed Packages
mesa-libGL.x86_64 6.5.2-13.fc7
installed
mesa-libGL.i386 6.5.2-13.fc7
installed
mesa-libGLU.x86_64 6.5.2-13.fc7
installed
mesa-libGLU.i386 6.5.2-13.fc7
installed
> Make sure that you have x86_64 libraries installed.
>
> [root@kursk lib]# yum list mesa-libGL mesa-libGLU
Thanks, I had them. I eventually figured out the full list of
packages required to compile enblend, these packages and their
dependencies are required to build 3.0 on fedora:
libtiff-devel boost-devel lcms-devel plotutils-devel freeglut-devel
glew-devel
These are the additional packages required to build 3.1:
libXmu-devel libXi-devel libjpeg-devel libpng-devel
--
Bruno
Don't know what this might be, though you can test to see if any of
the tools are failing by stitching the project directly with 'make':
Save (without stitching), you should get a 'project.pto.mk' Makefile
as well as the 'project.pto' file. In a terminal, run 'make' like
so:
cd /path/to/folder
make -f project.pto.mk
This should give you some idea where the problem is.
--
Bruno
>Illegal token in 'p'-line [69] [E] [E-0.607398 R0 n"TIFF_m c:DEFLATE r:CROP"]
>Illegal token in 'p'-line [82] [R] [R0 n"TIFF_m c:DEFLATE r:CROP"]
It looks like PTmender doesn't know about the new E & R parameters,
so it refused to do the stitch.
Is there any reason why you are using 'PTmender' instead of 'nona'
as your stitcher? 'nona' should be the default.
--
Bruno
Using `make install` to put something like hugin into /usr isn't
such a good idea as there is no easy way to remove all the files at
a later date. On debian/ubuntu you can use `checkinstall` which
will do the right thing and give you something you can remove with
dselect (or whatever you use these days on debian for package
management).
--
Bruno
It doesn't and maybe it should, but even if it did this would be
very fragile - On most linux distributions /usr is maintained
entirely by the package management system.
This is why we don't have to worry about linux systems getting
'clogged up', all I have to do is `rm -rf /usr/local && yum update`
and I have a system that is effectively as clean as a fresh install.
--
Bruno