plugin development commit

[ben.boeckel (Ben Boeckel (Kitware))]

@zetwal

GenericIO is relying on Blosc1, which it seems will be kept, which is good.

We do have to make sure that Blosc1 and Blosc2 don’t have any symbol names in common; if they do, things won’t go too well when both get loaded.

@zetwal

However, how do I automatically get the path to the install folder (paraview-superbuild_build/install) where the libraries are built?

Refer to <INSTALL_DIR> and the ExternalProject infrastructure will replace it for you.

@zetwal

now I need ParaView to get and build the SZ compressor. How do I do that?

You mean one of the vendored third party libraries? We generally don’t support that and will need to rely on an external copy. I believe the internal one provides implementations that always report “not supported” errors.

[zetwal (Pascal Grosset)]

@ben.boeckel

You mean one of the vendored third party libraries? We generally don’t support that and will need to rely on an external copy. I believe the internal one provides implementations that always report “not supported” errors.

The SZ compressor I am referring to is this: GitHub - szcompressor/SZ: Error-bounded Lossy Data Compressor (for floating-point/integer datasets). I downloaded the zip file from GitHub - szcompressor/SZ at v2.1.8.3 which I linked against to use.

[zetwal (Pascal Grosset)]

@ben.boeckel

Refer to <INSTALL_DIR> and the ExternalProject infrastructure will replace it for you.

I saw that CMAKE_PREFIX_PATH points to where the install folder is. So, I’m using that variable.