[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Package shared library with application



> > > Hi All,
> > >
> > >
> > > I'm trying to package my application together with a shared library that I have written but run now into following error:
> > >
> > >
> > > dpkg-shlibdeps: error: no dependency information found for /usr/lib/x86_64-linux-gnu/libkImageAnnotator.so.0.0.1 (used by debian/ksnip/bin/ksnip)
> > > Hint: check if the library actually comes from a package.
> > >
> > >
> > > After searching for a solution, I saw that some folks suggest, as a workaround, to add following to the rules:
> > >
> > >
> > > override_dh_shlibdeps:
> > >
> > >      dh_shlibdeps --dpkg-shlibdeps-params=--ignore-missing-info
> > >
> > >
> > > Is that a correct approach or just a hack that could cause later on problems?
> >
> > If you're only using the package internally, it's fine.
> >
> > If you're planning on offering the application to Debian or to
> > the public, you should make a separate package for
> > libkImageAnnotator or include it in this one formally.
> >
> > -dsr-
>
> Well, the .deb file is planned to be offered via my github release page, so I guess it's going to be publicly available. What do you mean with "include it in this one formally"?
> Can you recommend any tutorial or simple example? I usually don't package stuff so my knowledge about this topic is limited.  
>
> Thanks for your feedback!
>
> Damir


Even with this option set, I'm still failing failing to start the application after installing from package, I get an error saying: error while loading shared libraries: libkImageAnnotator.so.0.0.1: cannot open shared object file: No such file or directory

Any idea what the reason could be? The lib was installed under /usr/lib/


Reply to: