[Digikam-devel] [Bug 139658] Tiff generated by photoshop is either ignored by Digikam image browser, or kills digikam when regenerating the database

[Fabien]

Hello,

Gilles Caulier wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>          
> http://bugs.kde.org/show_bug.cgi?id=139658         
> 
> 
> 
> 
> ------- Additional Comments From caulier.gilles kdemail net  2007-01-09 07:48 -------
> 
>>There have been a few similar misunderstandings as it can be difficult for non-developer >users to trace library dependencies. I suggest to add a global function std::string >Exiv2::version() to exiv2 and digikam could use it in the about screen (or similar)
> 
> 
> Yes, i thinking the same issue since a long time. I'm doing the same way to display the libkipi version in About dialog. I will do it with Exiv2.
> 
> 
>>Another alternative might be a script which uses ldd and co. to list the dependencies and >extract soname info from the libraries. What do you think?
> 
> This can be a simple command line to use to debug.  This command can be given in web project page and HACKING file from svn. 
> 
> Fabien, what do you think about ?

Yes, why not.
I'll try to do that. It's mandatory to check with ldd not only digikam 
but also imageplugins and kipi-plugins as I remember I already have a 
case where digikam was correctly linked to the right version but not the 
  plugins (LD_LIBRARY_PATH can force digikam to use the library in a 
specific directory, but plugins use .la files if I'm not wrong).

But, I think it would still be useful to get the information within 
digikam. Eg, digikam could prompt a warning about a bit too old version 
and maybe also exit when started with a too old version...

--
Fabien