<br><br><div><span class="gmail_quote">2007/3/6, Achim Bohnet <<a href="mailto:ach@mpe.mpg.de">ach@mpe.mpg.de</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday, 6. March 2007, Dennis Veatch wrote:<br>> On Tuesday 06 March 2007 07:27:53 am Arnd Baecker wrote:<br>> > On Mon, 5 Mar 2007, Dennis Veatch wrote:<br>> ><br>> > [...]<br>> ><br>> > > Your right, did not realize jasper does not build .so by default.
<br>> ><br>> > Me neither, Fabien and Achim helped me through that<br>> > on the developers mailing list ;-)<br>> > (Funnily, it used to work before ...)<br>><br>> Yah that was my confusion because the 
0.9.0 configure had no issues with that<br>> and no other apps that can use it barked about it.... at least not that I<br>> have found yet.<br><br>that made me curious. and I greped 0.9 and 0.9.1 configure<br><br>$ grep -i jasper 
0.9.0/digikam-0.9.0/digikam/configure.in.in 0.9.1/digikam-0.9.1/digikam/configure.in.in<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:# Check for libjasper (JPEG2000)<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:have_jasper=no
<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:KDE_CHECK_LIB(jasper, jas_init,<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:              have_jasper=yes,<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:              AC_MSG_WARN([digiKam requires libjasper >= 
1.7.0]),<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:              -ljasper)<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:if test "x$have_jasper" != "xyes"; then<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:  AC_WARN([digiKam requires libjasper >= 
1.7.0; digiKam will not be compiled.])<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:  LIB_JASPER="-ljasper"<br>0.9.1/digikam-0.9.1/digikam/configure.in.in:  AC_SUBST(LIB_JASPER)<br><br>so 0.9.0 had no check for libjasper at all ;)
</blockquote><div><br>Absolutly. I have added jasper depency only with 0.9.1 release<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
grep -i jasper 0.9.0/digikam-0.9.0/README   find also nothing.<br>So my naive summary is that digikam did not use libjasper in 0.9.0<br><br>Searching recursively for jasper uncovered:<br>0.9.0/digikam-0.9.0/acinclude.m4:AC_DEFUN([AC_FIND_JASPER],
<br>0.9.0/digikam-0.9.0/acinclude.m4:AC_MSG_CHECKING([for jasper])<br>0.9.0/digikam-0.9.0/acinclude.m4:AC_CACHE_VAL(ac_cv_jasper,<br>0.9.0/digikam-0.9.0/acinclude.m4:LIBS="$LIBS $all_libraries $USER_LDFLAGS -ljasper $LIBJPEG -lm"
<br>0.9.0/digikam-0.9.0/acinclude.m4:    #include<jasper/jasper.h><br>0.9.0/digikam-0.9.0/acinclude.m4:    eval "ac_cv_jasper='-ljasper $LIBJPEG -lm'",<br>0.9.0/digikam-0.9.0/acinclude.m4:    eval "ac_cv_jasper=no"
<br>0.9.0/digikam-0.9.0/acinclude.m4:if eval "test ! \"`echo $ac_cv_jasper`\" = no"; then<br>0.9.0/digikam-0.9.0/acinclude.m4:  AC_DEFINE_UNQUOTED(HAVE_JASPER, 1, [Define if you have jasper])<br>0.9.0/digikam-
0.9.0/acinclude.m4:  LIB_JASPER="$ac_cv_jasper"<br>0.9.0/digikam-0.9.0/acinclude.m4:  AC_MSG_RESULT($ac_cv_jasper)<br>0.9.0/digikam-0.9.0/acinclude.m4:  LIB_JASPER=""<br>0.9.0/digikam-0.9.0/acinclude.m4:AC_SUBST(LIB_JASPER)
<br><br>as this check mentions  $LIBJPEG and -lm, which were the problem is<br>the static libjasper build AFAIR, I assume digikam should use AC_FIND_JASPER<br>instead it's home grown test?</blockquote><div><br>Well if it work why not... 
<br><br></div></div>Gilles<br>