Thank you Roman. I didn't realize darktable doesn't use the cli tool, but
had to be built against the exiv2 library. I rebuilt it with the correct
exiv2 installed and now it works!

Thanks,

Owen


On Wed, Mar 23, 2016 at 2:09 AM, Roman Lebedev <[email protected]> wrote:

> On Wed, Mar 23, 2016 at 8:31 AM, Owen Mays <[email protected]> wrote:
> > Hi all,
> >
> > I have a lens that isn't recognized by the current release version of
> exiv2,
> > but is supported in the development tree. I imported images from this
> > unrecognized lens, so darktable lists the lens as "173"  instead of the
> lens
> > name.
> >
> > I just built exiv2 from source and installed it, but now I have two
> versions
> > of exiv2 floating around on my machine. I thought they were:
> /usr/bin/exiv2
> > and /usr/local/bin/exiv2. I deleted the old one and made it a symlink to
> the
> > new one, so now on the command line if I run "exiv2" it lists the full
> name
> > of my lens.
> That /usr/bin/exiv2 is just a CLI tool, darktable does not and can not use
> it.
> Darktable needs exiv2 *library*.
>
> Just installing new library is not enough. A program must be re-compiled
> against new version. So just replacing .so probably won't be enough either.
> See ldd `whereis darktable` | grep exiv2 or something like that for
> it's location.
>
> Also, do remember that you will probably need to re-import old images
> in order to get dt to re-read lens info from them.
>
> > But the listing inside of darktable still just says "173." Is there
> > something else I need to do to force darktable to re-recognize the lens?
> Or
> > can someone tell me where darktable looks for exiv2 so I can be sure it's
> > not using an old version?
> >
> > Thanks in advance,
> >
> > Owen
> Roman.
>
> >
> ____________________________________________________________________________
> > darktable user mailing list to unsubscribe send a mail to
> > [email protected]
>

____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to