# Cannot get pvpython-real or pvserver-real from compiling and building from source
**URL:** https://discourse.paraview.org/t/cannot-get-pvpython-real-or-pvserver-real-from-compiling-and-building-from-source/15605
**Category:** ParaView Support
**Created:** [October 22, 2024, 7:40am UTC](https://discourse.paraview.org/t/cannot-get-pvpython-real-or-pvserver-real-from-compiling-and-building-from-source/15605 "2024-10-22T07:40:18Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@tigerhu](https://discourse.paraview.org/u/tigerhu)
#### Post date: [October 22, 2024, 7:40am UTC](https://discourse.paraview.org/t/cannot-get-pvpython-real-or-pvserver-real-from-compiling-and-building-from-source/15605/1 "2024-10-22T07:40:18Z")
Hello,
【My Problem】
I would like to compile and build paraview from sourcecode on a linux headless machine. I have followed official link [GithubParaviewBuildLink](https://github.com/Kitware/ParaView/blob/master/Documentation/dev/build.md), and succeeded somehow.
But when I compared mybuild with [KitwareOfficialHeadlessServerBinary](https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.13&type=binary&os=Linux&downloadFile=ParaView-5.13.1-osmesa-MPI-Linux-Python3.10-x86_64.tar.gz), I found -real executable files are not built (like pvpython-real, pvserver-real, but pvpython and pvserver are built successfully )
【Attemp I made】
I finds this might be helpful, but could not figure out how to utilize it.
[CUDA\_ARCHITECTURES — CMake 3.30.5 Documentation](https://cmake.org/cmake/help/v3.30/prop_tgt/CUDA_ARCHITECTURES.html)
Could anyone give me some advice? Thanks in advance!!
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 22, 2024, 7:49am UTC](https://discourse.paraview.org/t/cannot-get-pvpython-real-or-pvserver-real-from-compiling-and-building-from-source/15605/2 "2024-10-22T07:49:08Z")
The official binary is built using the ParaView Superbuild: [https://gitlab.kitware.com/paraview/paraview-superbuild](https://gitlab.kitware.com/paraview/paraview-superbuild), which uses the “launcher” project to create such an architecture.
In any case, this is is not an issue and you should be able to use your own build fine.
But why do you not use the official binary ?
I do not understand your question about CUDA though.
---
### Author:  [@tigerhu](https://discourse.paraview.org/u/tigerhu)
#### Post date: [October 22, 2024, 7:55am UTC](https://discourse.paraview.org/t/cannot-get-pvpython-real-or-pvserver-real-from-compiling-and-building-from-source/15605/3 "2024-10-22T07:55:33Z")
Thank you for the quick reply.
The reason is I want to add a vtk filter to Paraview, and this vtk filter is not included in official binary.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [October 22, 2024, 12:21pm UTC](https://discourse.paraview.org/t/cannot-get-pvpython-real-or-pvserver-real-from-compiling-and-building-from-source/15605/4 "2024-10-22T12:21:14Z")
Those binaries are there to leave room for the “official” names to be the [`launchers`](https://gitlab.kitware.com/paraview/paraview-superbuild/-/tree/master/launchers) binary. This sits between the user and the `-real` binaries so that it can inject environment settings to load the superbuild’s Mesa or MPI binaries instead of the system copies. If you’re not using the superbuild’s `mesa`, `osmesa`, or `mpi` projects, there’s no need for the launchers or `-real` binaries.