# build stand alone visitbridge with vtk
**URL:** https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619
**Category:** Support
**Created:** [June 22, 2020, 8:14pm UTC](https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619 "2020-06-22T20:14:37Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@kayarre](https://discourse.vtk.org/u/kayarre)
#### Post date: [June 22, 2020, 8:14pm UTC](https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619/1 "2020-06-22T20:14:37Z")
I would like to build standalone visitbridge with vtk and vtk bindings?. Is that possible?
I feel like I want more but not the whole paraview “kitchen sink” more
how much would the interface have to change?
generally I have not had much luck compiling paraview (the binary releases are great!)
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [June 22, 2020, 8:46pm UTC](https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619/2 "2020-06-22T20:46:06Z")
You could probably try compiling VisItBridge as an additional module in VTK. But this would be completely unsupported overall.
Have you filed issues about the problems you’ve encountered compiling ParaView?
---
### Author:  [@kayarre](https://discourse.vtk.org/u/kayarre)
#### Post date: [June 23, 2020, 1:07am UTC](https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619/3 "2020-06-23T01:07:00Z")
Thank you. I have not filed any. I will keep that in mind the next time I am brave enough to try again.
-Kurt
---
### Author:  [@kayarre](https://discourse.vtk.org/u/kayarre)
#### Post date: [June 24, 2020, 8:53pm UTC](https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619/4 "2020-06-24T20:53:27Z")
> [@ben.boeckel](#):
>
> You could probably try compiling VisItBridge as an additional module in VTK. But this would be completely unsupported overal
This is a great suggestion. The interesting thing is that besides the paraview specific xml file, the module looks like pure VTK.
Modifications include changing the module.vtk namesspace variables from `Paraview::` to `VTK::` ( Not sure if that was necesary? )
and made an option called “VISIT\_BUILD\_READER\_Paraview” that defaults to `ON` so that when it’s off it skips the paraview specific macro.
Does that seem like a reasonable approach?
Can one suggestion a “best practice” to support this approach internally.
e.g. have a vtk branch that tracks upstream with the additional module files?
and a branch for the VisItBridge repo with the same?
with this module `magic`, I think self support is doable.
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [June 24, 2020, 9:51pm UTC](https://discourse.vtk.org/t/build-stand-alone-visitbridge-with-vtk/3619/5 "2020-06-24T21:51:39Z")
It sounds like it’d work. VisItBridge itself is a git submodule of ParaView, so you could probably just reuse it with your own branch which handles the conditions.