# native vtkProcessXML for cross-compilation ?

**URL:** https://discourse.paraview.org/t/native-vtkprocessxml-for-cross-compilation/9810
**Category:** Development
**Created:** [June 14, 2022, 3:52pm UTC](https://discourse.paraview.org/t/native-vtkprocessxml-for-cross-compilation/9810 "2022-06-14T15:52:29Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jschueller](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jschueller/32/7736_2.png) [@jschueller](https://discourse.paraview.org/u/jschueller)
#### Post date: [June 14, 2022, 3:52pm UTC](https://discourse.paraview.org/t/native-vtkprocessxml-for-cross-compilation/9810/1 "2022-06-14T15:52:29Z")

</div>

in cross-compilation mode we need a native version of the vtkProcessXML executable that is part of paraview when no emulator is available

I dont seem to find a paraview equivalent of VTK\_BUILD\_COMPILE\_TOOLS\_ONLY though, is there a way to do that ?

[@ben.boeckel](https://gitlab.kitware.com/ben.boeckel) maybe ?

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [September 7, 2022, 8:54pm UTC](https://discourse.paraview.org/t/native-vtkprocessxml-for-cross-compilation/9810/2 "2022-09-07T20:54:51Z")

</div>

No, ParaView hasn’t had any effort put into its cross-compilation (the ClientServer wrapping tools would also need to be part of that build).