) writes a header file you can include
# in your sources to initialize the static python modules
function(PYTHON_ADD_MODULE _NAME )
# check for shared library property
get_property(_TARGET_SUPPORTS_SHARED_LIBS
GLOBAL PROPERTY TARGET_SUPPORTS_SHARED_LIBS)
# add options
option(PYTHON_ENABLE_MODULE_${_NAME} "Add module ${_NAME}" TRUE)
option(PYTHON_MODULE_${_NAME}_BUILD_SHARED
"Add module ${_NAME} shared" ${_TARGET_SUPPORTS_SHARED_LIBS})
# mark these options as advanced
mark_as_advanced(
PYTHON_ENABLE_MODULE_${_NAME}
PYTHON_MODULE_${_NAME}_BUILD_SHARED
)
# add python module
if(PYTHON_ENABLE_MODULE_${_NAME})
if(PYTHON_MODULE_${_NAME}_BUILD_SHARED)
set(PY_MODULE_TYPE MODULE)
else()
set(PY_MODULE_TYPE STATIC)
set_property(GLOBAL APPEND PROPERTY PY_STATIC_MODULES_LIST ${_NAME})
endif()
# add library
set_property(GLOBAL APPEND PROPERTY PY_MODULES_LIST ${_NAME})
add_library(${_NAME} ${PY_MODULE_TYPE} ${ARGN})
# target_link_libraries(${_NAME} ${PYTHON_LIBRARIES})
# set library prefix
if(PYTHON_MODULE_${_NAME}_BUILD_SHARED)
set_target_properties(${_NAME} PROPERTIES PREFIX "${PYTHON_MODULE_PREFIX}")
if(WIN32 AND NOT CYGWIN)
set_target_properties(${_NAME} PROPERTIES SUFFIX ".pyd")
endif()
endif()
endif()
endfunction()
```
---
### Author:  [@StRuoff](https://discourse.paraview.org/u/StRuoff)
#### Post date: [September 14, 2022, 2:34pm UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/7 "2022-09-14T14:34:31Z")
Another note I forgot to mention, that may explain the different behavior:
My local install (with custom built paraview) is with paraview Version 5.6.0.
The reason why I wanted to switch to the Easy-Builder was indeed, that I couldn’t get the plugin to work with newer paraview versions.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 14, 2022, 2:41pm UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/8 "2022-09-14T14:41:39Z")
Well, you want to make your plugin work with 5.10 locally first.
---
### Author:  [@StRuoff](https://discourse.paraview.org/u/StRuoff)
#### Post date: [September 15, 2022, 8:22am UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/9 "2022-09-15T08:22:50Z")
That’s what I wanted to avoid, since I would have to completely install paraview 5.10.0 from source locally.
Isn’t there any example, on how to wrap a plugin to the vtk/paraview python? Or at least a hint, on where to put the python-library, so that pvpython can find it?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 15, 2022, 9:03am UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/10 "2022-09-15T09:03:33Z")
> [@StRuoff](#):
>
> That’s what I wanted to avoid, since I would have to completely install paraview 5.10.0 from source locally.
This is really easy to do the guide is here:
[https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/build.md#getting-started-guide](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/dev/build.md#getting-started-guide)
> Isn’t there any example, on how to wrap a plugin to the vtk/paraview python? Or at least a hint, on where to put the python-library, so that pvpython can find it?
The wrapping si automatic and should not require anything specific in your plugin. You should be able to load your plugin and just use the python shell as if the code you built is part of actual paraview.
---
### Author:  [@StRuoff](https://discourse.paraview.org/u/StRuoff)
#### Post date: [September 15, 2022, 1:22pm UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/11 "2022-09-15T13:22:08Z")
Ok, So I think I found the solution (or rather my error):
When I finished building the Plugin, I copied it to `$PARAVIEW_DIR/plugins` instead of `$PARAVIEW_DIR/lib/paraview-5.10./plugins`.
Now the plugin is automatically found by paraview and can be imported via
`from paraview.simple import vtkThetaReader`
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 15, 2022, 1:25pm UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/12 "2022-09-15T13:25:41Z")
Ok, but I want to mention that you are not supposed to put your own plugins there, there is dedicated mechanism for that.
---
### Author:  [@StRuoff](https://discourse.paraview.org/u/StRuoff)
#### Post date: [September 15, 2022, 1:40pm UTC](https://discourse.paraview.org/t/wrap-plugin-with-python-for-superbuild/10315/13 "2022-09-15T13:40:37Z")
I see…
I reread all the info on the Plugins from the [HowTo](https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Using_Plugins) and found another mistake I (unintenionally) made:
I forgot to set the `PV_PLUGIN_PATH` variable.
When I set it to point to the `$PARAVIEW_DIR/plugins` folder, everything loads fine and also the python-import still works as expected.