The problem is not where they are installed (as long as they are where KiCad looks for them), but against which dynamic (KiCad) library (and, what locations) they are linked. The guy providing his plugin might have linked against /usr/lib/… whereas the other guy installing it in his user KiCad plugin folder has his KiCad installed in /opt/… And, to get more fun, probably he also has some older version installed by distribution in ldconfig before /opt/… Guess if the plugin will grab the right one?
> On 20 Apr 2016, at 17:13, Nick Østergaard <[email protected]> wrote: > > But in the case of binary plugins, theu would be installed to the same search > location where kicad is already looking so the ldconfig should not be > problem, should it? > > Den 20/04/2016 16.04 skrev "Bernhard Stegmaier" <[email protected] > <mailto:[email protected]>>: > ... these dynamic linked library issues will be really fun when/if we start > with user-plugins, especially if they are distributed as a binary and maybe > not distributed by any official package maintainer of a distribution ... > > > Regards, > Bernhard > > On 2016-04-20 10:11, Mário Luzeiro wrote: > I experienced that also but, for some reason that I dont understand > how it works, it starts to work again. > So maybe just need a reboot to make that "ldconfig update its cache". > ________________________________________ > From: Kicad-developers > [[email protected] > <mailto:[email protected]>] on > behalf of Cirilo Bernardo [[email protected] > <mailto:[email protected]>] > Sent: 20 April 2016 04:46 > To: Tiger12506 > Cc: KiCad Developers > Subject: Re: [Kicad-developers] libkicad_3dsg.so.2.0.0 > > This issue is due to a required shared library being installed to > a path which is not currently checked by ldconfig. In your case > the path is /usr/local/lib. You will need to configure ldconfig to > look for shared libraries in /usr/local/lib, then run ldconfig to > update its cache. This is not a bug, it is an issue that needs to > be addressed by package maintainers and users who build and > install from source. Since different Linux systems manage the > ldconfig configuration in different ways it makes no sense for > KiCad developers to attempt to manage this configuration via the > CMake install scripts. > > - Cirilo > > > On Wed, Apr 20, 2016 at 1:20 PM, Tiger12506 > <[email protected] > <mailto:[email protected]><mailto:[email protected] > <mailto:[email protected]>>> wrote: > A little problem when I compiled the latest bazaar revision. > > A kicad that runs, but trying to open pcbnew results in error. Also > occurs when trying to run pcbnew standalone. > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > More help : https://help.launchpad.net/ListHelp > <https://help.launchpad.net/ListHelp> > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > More help : https://help.launchpad.net/ListHelp > <https://help.launchpad.net/ListHelp>
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
