vpp/docs/gettingstarted/developers/plugins.rst

.. _dplugins:

Plugins
=======

vlib implements a straightforward plug-in DLL mechanism. VLIB client
applications specify a directory to search for plug-in .DLLs, and a name
filter to apply (if desired). VLIB needs to load plug-ins very early.

Once loaded, the plug-in DLL mechanism uses dlsym to find and verify a
vlib\_plugin\_registration data structure in the newly-loaded plug-in.

For more on plugins please refer to :ref:`add_plugin`.
DOCS: Moved multiarch and build system, Incorprated Scott's changes Change-Id: I5a57846db2d4faac1aa24db4629b612657f59afb Signed-off-by: John DeNisco <jdenisco@cisco.com> 2018-08-14 16:04:09 -04:00			`.. _dplugins:`
Initial commit of Sphinx docs Change-Id: I9fca8fb98502dffc2555f9de7f507b6f006e0e77 Signed-off-by: John DeNisco <jdenisco@cisco.com> 2018-07-26 12:45:10 -04:00
			`Plugins`
			`=======`

			`vlib implements a straightforward plug-in DLL mechanism. VLIB client`
			`applications specify a directory to search for plug-in .DLLs, and a name`
			`filter to apply (if desired). VLIB needs to load plug-ins very early.`

			`Once loaded, the plug-in DLL mechanism uses dlsym to find and verify a`
			`vlib\_plugin\_registration data structure in the newly-loaded plug-in.`

DOC ONLY: clean up plugin documentation The old "sample_plugin" page was stuffed with superceded autotools build information, so it morphed into an "add a new plugin" page based on the emacs-lisp plugin generator. Before sending hate mail about emacs, please look at the new document: you'll find running the plugin generator hard to tell from running a shell script. Change-Id: I84da45675e838c05faeca05c8f7be45d8c7bff13 Signed-off-by: Dave Barach <dave@barachs.net> 2018-10-04 17:12:26 -04:00			For more on plugins please refer to :ref:`add_plugin`.