[Digikam-devel] compile from svn problem

Arnd Baecker arnd.baecker at web.de
Thu Mar 1 18:14:23 GMT 2007


On Thu, 1 Mar 2007, Achim Bohnet wrote:

[...]

> > > > However, libjasper is installed
> > > > digikam/lib $ ls -l | grep jasper
> > > > -rw-r--r-- 1 abaecker abaecker 1266404 Mar  1 14:51 libjasper.a
> > > > -rwxr-xr-x 1 abaecker abaecker     817 Mar  1 14:51 libjasper.la
>
> Your problem is here.  You only have a static version off libjasper
> Install/build the shared one.

OK.
But why did I never have any problems before?
(I.e., the last months, since jasper was required
I happily ran svn with the above library ;-)

BTW, by default, the shared library is not built
(I use jasper-1.900.0.zip),  and one has to use
  ./configure --prefix=$DIGIKAMDEST --enable-shared
which will then lead to libjasper.so.1.0.0 + symbolic links.

Many thanks,

Arnd


P.S.: This reminds me, that the text at
http://www.digikam.org/?q=download/svn
should be updated.

Suggestion, after the "(download compile_exiv2.sh script)" block:

"""
Installation of
<a href="http://www.ece.uvic.ca/~mdadams/jasper/">libjasper</a>
(don't forget to replace DIGIKAMDEST value)

wget http://www.ece.uvic.ca/~mdadams/jasper/software/jasper-1.900.1.zip
unzip jasper-1.900.1.zip
cd jasper-1.900.1
export DIGIKAMDEST=/home/fabien/myopt
./configure --prefix=$DIGIKAMDEST --enable-shared
make
make install
cd ..
"""

Fabien, could you maybe add the above?



More information about the Digikam-devel mailing list