On Tuesday, 13 August 2013 08:26:51 CEST, Pali Rohár wrote:
Yes, I want to support also this configuration. But not only this.
What are the benefits of this? "There will be no shared library" is not a
benefit, that's a statement of fact. I want to know *why* it is important
to you to work without any shared library.
Some reasons on why I believe that it is not worth the effort:
- it requires extra code -> increased future maintenance
- it works only on GCC
- the linker flags one needs could be considered hackish
- it goes against the general plugin recommendations
- Trojita already links against a myriad of shared libraries
- the solution requires code duplication in both Trojita-the-binary and
each .so plugin (speaking about the code segment in the resulting ELF),
thereby wasting memory, as per what Thiago said
- one would be, effectively, linking the plugin against the
/usr/bin/trojita, if I understand Thiago correctly
What I'm interested to know is a similar list of benefits -- could you
please provide one?
No. Runtime loading should work too (at least with GCC). For GNU
compiler/linker is needed special flag, but this is added by cmake
when using GNU. Also if some password and some addressbook
plugins will be statically linked into trojita executable, it
will not be needed anymore.
OK, I stand corrected and am not including "it will disable runtime plugin
loading" in the list of drawbacks.
Jan
--
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
