On Monday 12 August 2013 22:36:26 Jan Kundrát wrote: > On Monday, 12 August 2013 22:06:17 CEST, Thomas Lübking wrote: > > Jus compile them directly into the core then? (implicitly > > linking the shared library since the core does) > > They way I understand it, Pali wants to support a > configuration where there are no shared libraries, just the > /usr/bin/trojita with some plugins statically linked in. > (Pali, please correct me if I'm wrong.) >
Yes, I want to support also this configuration. But not only this. > To my understanding, this will effectively prevent any runtime > loading of plugins unless they're built with custom LDFLAGS > and similar tweaks. If all of the above is right, I do not > see a point in supporting the static linkage. Sure, it will, > well, enable static linkage, but *why* do we want to get rid > of that shared library dependency? > 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. -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
