Commit 038b3c3f authored by Ben Boeckel's avatar Ben Boeckel Committed by Kitware Robot

Merge topic 'plugin-path-doc-update' into release

af6e1634 doc: mention relative filename entries
8cf3e819 doc: mention that plugin subdirs are supported as well
Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
Acked-by: Mathieu Westphal's avatarMathieu Westphal <mathieu.westphal@kitware.com>
Merge-request: !3905
parents 193f9edd af6e1634
Pipeline #160205 failed with stage
in 0 seconds
......@@ -81,7 +81,9 @@ There are four ways for loading plugins:
on startup to load plugins. This environment variable needs to be set on
both the client and server sides to load their respective plugins. Note
that plugins in PV_PLUGIN_PATH are always auto-loaded irrespective of the
status of the `Auto Load` checkbox in the `Plugin Manager`.
status of the `Auto Load` checkbox in the `Plugin Manager`. Paths in this
list may also be of the structure created by the ParaView plugin macros
(e.g., `MyPlugin/MyPlugin.so`).
- Finer control can be used using the `PV_PLUGIN_CONFIG_FILE` environment
variable. `PV_PLUGIN_CONFIG_FILE` can be used to list a set of XML plugin
configuration files (separated by colon (`:`) on Unix platforms or
......@@ -93,6 +95,8 @@ There are four ways for loading plugins:
<?xml version="1.0"?>
<Plugins>
<Plugin name="MyPlugin" filename="/absolute/path/to/libMyPlugin.so"/>
<!-- Note that relative paths are calculated from the directory of this XML file. -->
<Plugin name="MyPluginRel" filename="relative/path/to/libMyPlugin.so"/>
</Plugins>
```
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment