Lines Matching full:plugins

3 Lws now offers apis to manage your own user plugins with `LWS_WITH_PLUGINS_API`.
4 Lws uses these apis internally for protocol plugins and event loop plugins
12 Lws plugins have a single exported struct with a specified header and a user
38 `_class` is shared by your plugins and used to select them from other kinds
40 `"myapp xxx plugin"` or whatever shared by all plugins of that class.
60 ## Building your own plugins
62 Plugins are built standalone, cmake is recommended but you can do what you want.
79 ## Bringing in plugins at runtime
81 Lws provides an api to import plugins into the process space and another to
82 remove and destroy plugins.
85 later destroy a whole class of plugins at once, and walk them via a linked-list,
89 See `include/libwebsockets/lws-protocols-plugins.h` for documentation.
103 plugins and a pointer to its exported header object, so you can walk this