-
Notifications
You must be signed in to change notification settings - Fork 123
rename all plugins's .so
s
#3486
Comments
I agree with this proposal, and there is no better time to do this than pre-1.0. 👍 |
@kodebach any thoughts on this? |
Yes, adding a
Since Additionally, I would also change typedef Plugin * (*elektraPluginFactory) (void); to typedef KeySet * (*elektraPluginFactory) (void); where the returned |
Thank you for your input! I have split the issues: this issue is only about renaming: adding the |
@tmakar last issue for you: spec plugin should be renamed to libelektra-plugin-spec.so (and likewise for all other plugins) |
@tmakar One way this issue can definitely be solved is by adding the
IMO this would be the best option, but it will probably require more changes to CMake elsewhere, since this changes the name of the CMake targets for plugins. CMake also supports setting an
to set the |
Thanks for the details!! |
@markus2330 PR exists in #4919. |
Set new target name for so files (#3486)
As @poldi871reported in #3472 on embedded systems (with the cmake option
TARGET_PLUGIN_FOLDER=""
)kdb plugin-list
reports both libraries and plugins. Also by looking at the names of the.so
s you cannot know what a plugin is.An easy fix for both problems would be to rename the
.so
s to e.g.libelektra-plugin-toml.so
instead oflibelektra-toml.so
. This is a bit redundancy in the caseTARGET_PLUGIN_FOLDER!=""
but helpful in many other situations (e.g. when looking into thelib
folder of the cmake build dir), e.g. on my system (wherekdb get system/info/elektra/constants/cmake/BUILTIN_PLUGIN_FOLDER
returns/usr/lib/x86_64-linux-gnu/elektra4
the plugins would be called e.g./usr/lib/x86_64-linux-gnu/elektra4/libelektra-plugin-toml.so
.So I propose to do this rename. Obviously it is an incompatible change: Elektra needs to be fully reinstalled as the new core would only find newly installed plugins (and not the ones with the old name). Furthermore, I propose (maybe even the bigger change in terms of work) that we drop the name "modules". Instead, only the name "plugin" should be used for plugins, even on loader level. E.g. elektraModulesLoad would be renamed to elektraPluginLoad. I also think that these 3 functions for plugin loading should be public, as they are handy in many situations (e.g. for import/export configuration).
What do you think?
The text was updated successfully, but these errors were encountered: