[Paraview-developers] general error loading plugins on Cray

[Chuck Atkins]

> Depending on whether your compile with the Cray wrapper, or with g++,
> you'll get a different behavior; the Cray wrapper automatically sets a
> -DCRAYXT_COMPUTE_LINUX_TARGET
>

Ugh, this is leftover from an older time.


Well, compiling with shared libs, I really should be able to open the
> shared libs objects. I have modified the source code of
> VTK/Utilities/KWSys/vtksys/DynamicLoader.cxx to default to the last case
> called " // 6. Implementation for default UNIX machines."
>

I reworked a lot of the Cray toolchain support in newer CMake versions so
CMake knows how to interpret and introspec the Cray wrappers (See
Modules/Compiler/CrayPrgEnv*).  Using a newer CMake (>= 3.6) then CMake
should be correctly determining whether or not shared libraries are
supported.  Using that, we should be able to use the global property
"TARGET_SUPPORTS_SHARED_LIBS" to set a #define in the kwsys configured
header file.  This, I believe, would be a better way to handle it rather
than searching for various #ifdefs in the c++ code, since CMake already
knows way more about differemt platforms and compilers that this dynamic
loader source file does.  I'll submit the patch to kwsys and give you a
like to the review so you can test it if you'd like.



> I am now up and running with PV5.2 on the Cray XC, running EGL.
>

Woo hoo! For what it's worth, we also run on a lot of CPU-only Crays using
OSMesa and OpenSWR, both old and new Crays (i.e. CLE5 and CLE6).

- Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161123/1cbbf670/attachment.html>