Created attachment 445354 [details, diff] Patch for gtk+-3.18.9.ebuild I am interested in statically linking my code against GTK+, and would like to request the addition of the static USE flag to current and future ebuilds for the x11-libs/gtk+ package. This would involve changing two lines in the ebuild (see attachment) and give users an easy switch to build the static libs.
You mean a "static-libs" use flag. A "static" use flag would control the linking of the few binaries installed by x11-libs/gtk+.
Created attachment 445470 [details, diff] Example patch for gtk+-3.18.9.ebuild Oops, you are correct - I meant a static-libs USE flag. Thank you!
I think we had a conversation long ago that a static gtk+ is basically non-functional, did I misunderstand ?
I am unaware of this earlier discussion. Do you mean disfunctional technically, or because of the LGPL? I want a statically linked binary executable to copy to a different (small, embedded) system without installing all the libraries. Even if releasing the code, I think static linking means you'd need to release the *object files* rather than the source code (third parties must be able to *relink* against a new GTK+ version, not recompile).
Technically. Though I'm not sure this was correct; the references I find are generally about it not being possible on Windows specifically, but theoretically possible on POSIX systems. Does it work for you, up to your statically linked application working fine? Though I'm not sure how you'll plan to meet the LGPL requirements of relinking possibilities when building out of Gentoo packaging. Sounds like some FEATURES=keepwork and some extra management to do anyways; or something else.
See also: https://projects.gentoo.org/qa/policy-guide/installed-files.html#pg0302
ago@, I don't know why you are drive-by adding an invalid blocker here; so removing and CCing for awareness.
We have no plans to add static-libs support to gtk+ due to aforementioned reasons. Closing the bug for now.
