[Github-comments] [geany/geany] Feature request: Please provide an AppImage for Geany (#1303)

Colomban Wendling notifications at xxxxx
Tue Nov 22 23:20:11 UTC 2016


> What about a list of runtime dependencies for `geany` and `geany-plugins` on CentOS 7 that aren't X or GDK-related? If I had that I could satisfy both of you, @b4n and @eht16.

Geany has basically zero deps.  You might want to bundle a version of `libvte9` because newer systems don't have that, but it's an optional runtime dependency for embedded terminal support.

GP it's a whole different story.  Check the libraries each plugins checks for.  Or once built, run `ldd` or similar to see the deps list, and filter that using good judgment -- or use a better command that only lists direct dependencies, but I don't have that under the hand right now, yet I'm sure it exists, maybe some options for objdump?

> Oh and which libraries included are X or GDK related? Out of:

Basically, everything that starts with `libX` or `libx` is X-related, so is `pixman`.  `libgdk` and `libatk` are GTK related, so are all of `pango`, `cairo`, `freetype`, `harfbuzz`, `png`.  `EGL`, `gl` and `gbm` are OpenGL related, so X/GTK.  `gmodule` and `gthread` are safe to assume I guess, GTK requires them anyway, and even maaaaany non-GUI apps.  `libffi` is GLib-related, and we don't depend on it directly so again, no use.  I have no clue about `libgraphite2` or `lzma` just now, but we don't depend on that directly either.  Which leaves us with… `libgeany`.  Better pack that last one :)

But really, you should find a way to *automatically* list first-levels deps.  LD must be able to help at some level, at least if building with `--as-needed` or something.

> @b4n I also run `yum-builddep geany geany-plugins` before I start the build. So if that doesn't cause all the build dependencies to be present I don't know what will.

Well, I can't know for sure, that must bring in what the author of the Fedora package said was required, that's all.  If you want to ship some plugins, I really recommend using explicit `--enable-<plugin>` flags so the configure pass explicitly fails if the dependencies aren't met.

But I really think it's rather an improper target location for the actual plugin binaries that not building *any* GP plugins.

> Well I've updated my AppImage to include the changes I think you want […] I tested it on Arch Linux and it works on there now. It also works on Fedora 24, so @b4n was right about those libraries.

Good.

-- 
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/issues/1303#issuecomment-262395603
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20161122/ff3bad1d/attachment.html>


More information about the Github-comments mailing list