[Github-comments] [geany/geany-plugins] Debugger plugin missing in Geany 1.37.1 compiled for Ubuntu 18.04 on Nvidia Jetson Nano (#1116)

[elextr]

> The packages appear to work for Ubuntu 20.04 and 21.10. I don't have 18.04 or 21.04 installed anymore.

Possibly the ld bug I linked above is fixed in those later distro releases.

>  If the Geany include files are present in both locations, trying to build the plugins just won't work -period- (Murphy's Law).

Presumably the distro standard library directory is searched before the local one (I think thats intended).  So if the distro version is installed, thats the only place plugins will be found, and they may not be compatible with your local Geany.

Unless explicitly supported never install two versions of the same software to system directories (rule for most SW not just Geany).  You can build Geany from tarball with any prefix, I use `~/geany-XXX` where I have a heap of XXXs and that will work because autotools adds an internal search path if the prefix is not a system directory.  I don't install to system directories because my distro puts libraries in `lib/x86-64_linux_gnu` but autotools puts Geany in /lib :frowning_face:.  This is one of the things @kugel-s meson build fixes for Geany.

> the dpkg system was probably not being used to build deb packages.

Yes, since the OP built a version newer than the distro they were using, probably Geany release tarballs.

> But usually building fails when dependencies aren't installed.

Yes, most dependencies should be tested for, but anyway the build will fail if the development version isn't installed.  But the `pluginutils` library is part of GP so its not a dependency.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1116#issuecomment-960352975
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20211103/234bbe89/attachment-0001.htm>