Mercurial > hg > orthanc-book
view Sphinx/source/developers/creating-plugins.rst @ 92:a3d3ff83024d
attachments doc + build with docker
author | amazy |
---|---|
date | Wed, 08 Feb 2017 20:22:42 +0100 |
parents | a3050705d836 |
children | 19dd28b3a541 |
line wrap: on
line source
.. _creating-plugins: Creating new plugins ==================== The recommended way of :ref:`contributing to the Orthanc code <contributing>` consists in extending it by creating new :ref:`plugins <plugins>`. Overview -------- Orthanc plugins must use the `plugin SDK <http://sdk.orthanc-server.com/>`__ and must be written in C or C++. They must also fullfil the terms of the `GPLv3 license <http://www.gnu.org/licenses/quick-guide-gplv3.en.html>`__ that is used by the core of Orthanc. Sample code for plugins can be found `in the official Orthanc repository <https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/>`__ (in the ``Plugins/Samples`` folder). A tutorial showing how to implement a basic WADO server is `available on CodeProject <http://www.codeproject.com/Articles/797118/Implementing-a-WADO-Server-using-Orthanc>`__. We suggest developers to adopt the :ref:`coding style of the Orthanc core <coding-style>`, although this is of course not required. Do not hesitate to `contact us <http://www.orthanc-server.com/static.php?page=contact>`__ if you wish your plugin to be **indexed** in :ref:`the dedicated part of the Orthanc Book <plugins-contributed>`! Structure of the plugins ------------------------ A plugin takes the form of a shared library (``.DLL`` under Windows, ``.so`` under GNU/Linux, ``.dylib`` under Apple OS X...) that uses the `ABI of the C language <https://en.wikipedia.org/wiki/Application_binary_interface>`__ to declare 4 public functions/symbols: * ``int32_t OrthancPluginInitialize(OrthancPluginContext* context)``. This callback function is responsible for initializing the plugin. The ``context`` argument gives access to the API of Orthanc. * ``void OrthancPluginFinalize()``. This function is responsible for finalizing the plugin, releasing all the allocated resources. * ``const char* OrthancPluginGetName()``. This function must give a name to the plugin. * ``const char* OrthancPluginGetVersion()``. This function must provide the version of the plugin. *Remark:* The size of the memory buffers that are exchanged between the Orthanc core and the plugins must be below 4GB. This is a consequence of the fact that the Orthanc plugin SDK uses ``uint32_t`` to encode the size of a memory buffer. We might extend the SDK in the future to deal with buffers whose size if above 4GB.