PARAVIEW_INSTALL DEVELOPMENT_FILES still used in ParaView 5.7?

I would like to know if the option PARAVIEW_INSTALL_DEVELOPMENT_FILES is still used in ParaView5.7. It seems it only adds some tests for ctest but has no real impact on the install process.
So my questions are:

  • Is this option still useful ?
  • Is it the default ParaView’s behavior to install its development files now ?
  • Can we build ParaView plugin against a Paraview install folder in the v5.7 ?

It seems it only adds some tests for ctest but has no real impact on the install process.

Oh, that’s an oversight. Which direction (removal was skipped or it doesn’t affect the install) is up for debate.

Is this option still useful ?

Personally, I don’t think so, but maybe others do.

Is it the default ParaView’s behavior to install its development files now ?

Yes.

Can we build ParaView plugin against a Paraview install folder in the v5.7 ?

Yes! :slight_smile:

Great ! Is there a roadmap for an actual binary SDK release ?

No, shipping an SDK is a harder problem. Though plausible on Windows because Visual Studio is so uniform and easy to describe, but the other platforms have issues with how to build compatible plugins. Nevermind using that SDK to make redistributable plugins (generally requiring building on CentOS6 with a devtoolset for Linux; probably some other shenanigans for macOS).