[CMake] Weirdness with shared library, RPATH policy on MacOS

[Martin Costabel]

Chris Wolf wrote:
[]
> It's interesting that you had a problem with this approach and python
> modules - I had a similar issue and ending up statically linking the 
> module because I had two releases of the same shared library on the system.

This is probably not a problem in cmake itself, but a problem with how 
VTK uses cmake. Bur I don't claim to understand this; I just dug deep 
enough to find a workaround.

-- 
Martin