PARAVIEW_BUILD_EDITION controls which modules within the ParaView build itself are enabled/disabled. The superbuild, on the other hand is used to build external libraries together with ParaView. PARAVIEW_BUILD_EDITION does not impact the Superbuild. You have manually enable / disable external libraries you want the superbuild to build.
Ah thank you, that makes sense now.
But then how can I customize the Paraview build itself when building through superbuild? Do, by chance, get any -DPARAVIEW_ENABLE_....=ON flags applied to superbuild used for building Paraview?
The superbuild will control what it can (e.g., it knows that it built ffmpeg and will therefore tell paraview about it). Same with any other projects which affect it (see the DEPENDS_OPTIONAL list). Basically, if the option you want to set is mentioned in projects/paraview.cmake, work with the superbuild to manipulate that flag.
For anything else, there is the superbuild’s PARAVIEW_EXTRA_CMAKE_ARGUMENTS variable (visible in the advanced view) which allows you to pass other cmake flags (;-separated) to ParaView’s configuration.
They aren’t passed directly; I suspect it is just ParaView finding the same paths that you passed in on its own. You can see all of the flags passed to ParaView’s configure in superbuild/sb-paraview-configure.cmake.