<br><br><div class="gmail_quote">2009/7/30 Vlado Plaga <span dir="ltr"><<a href="mailto:rechner@vlado-do.de">rechner@vlado-do.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am Thu, 30 Jul 2009 18:25:01 +0200<br>
schrieb Vlado Plaga <<a href="mailto:rechner@vlado-do.de">rechner@vlado-do.de</a>>:<br>
<div class="im"><br>
> I haven't finished compiling "beta 3" on Mac OS yet, but since that<br>
> might take a few hours, I'm already sending this e-mail now. At least<br>
> it downloaded the sources and started compiling.<br>
<br>
</div>Now compilation finished, but the program again crashes immediately<br>
after startup.<br>
<br>
Note: I had to manually patch<br>
digikam-1.0.0-beta3/libs/3rdparty/lqr/lqr_energy_priv.h<br>
<br>
like this:<br>
<a href="http://trac.macports.org/browser/trunk/dports/graphics/liblqr/files/patch-lqr__lqr_energy_priv.h?rev=51312" target="_blank">http://trac.macports.org/browser/trunk/dports/graphics/liblqr/files/patch-lqr__lqr_energy_priv.h?rev=51312</a><br>
<br>
The author of liblqr is aware of the problem, so in the next release it<br>
should be fixed:<br>
<a href="http://liblqr.wikidot.com/forum/t-169529/small-patch-needed-to-compile-liblqr-on-mac-os:change-upstream-package" target="_blank">http://liblqr.wikidot.com/forum/t-169529/small-patch-needed-to-compile-liblqr-on-mac-os:change-upstream-package</a><br>
<br>
I guess it is something of a philosophical question why digiKam brings<br>
its own private version of a library, instead of using the system<br>
version (which in MacOS/MacPorts is already patched)... </blockquote><div><br>In fact, it is supposed to use by default the system version and use the private version only if no system version can be found. <br>This means that the detection of the library is broken on MacOS.<br>
<br>I think the reason we keep a private copy of the library is that it was easier for the user to compile digikam. I guess that when lqr will be properly packaged in all main distributions and that the detection of the library works properly the private version of library will be removed from digikam.<br>
It was added at a time when we were using a version of lqr which was not released.<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
or why<br>
functionality such as this is included at all, although everyone using<br>
digiKam might as well use the Gimp for complex image editing functions.<br>
<div class="im"></div></blockquote><div><br>The gimp lqr plugin is more complicated to use than Digikam's one, it is adapted to the philisophy of gimp using layers, but not everyone wants to use/understand layers.<br>
IMHO Liquid rescale is not such a complex image editing function (from the user point of view). <br><br>Regards,<br><br>Julien <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
Regards,<br>
Vlado<br>
<br>
--<br>
<br>
Vlado Plaga __o<br>
<a href="http://vlado-do.de" target="_blank">http://vlado-do.de</a> _o/\<,_<br>
update: 14.03.2009 (U)/ (u)<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
</div>_______________________________________________<br>
Digikam-users mailing list<br>
<a href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-users</a><br>
</blockquote></div><br>