#787 Tulip fails to configure with CMake >= 3.1.0

[Raphael Kubo da Costa]

Tulip 4.6.0 (as well as svn trunk as of r10515) fails to configure with CMake 3.1.0 if OpenMP support is turned on.

For 4.6.0, the CMake backtrace looks like this:

CMake Error at CMakeLists.txt:111 (SET_TARGET_PROPERTIES):
  INTERFACE_LIBRARY targets may only have whitelisted properties.  The
  property "INSTALL_RPATH" is not allowed.
Call Stack (most recent call first):
  /usr/local/share/cmake/Modules/FindThreads.cmake:207 (add_library)
  CMakeLists.txt:232 (FIND_PACKAGE)

That's because Tulip overrides CMake's builtin add_library and add_executable functions. The easiest workaround is to just stop setting the INSTALL_RPATH property if the target's type is "INTERFACE_LIBRARY", but from a broader perspective it makes more sense to stop overriding those commands and build on top of them instead, so that that code is only called by the CMake code in Tulip itself, not from other CMake modules. Whether it makes sense to set the RPATH is also debatable, as distros such as Debian and Fedora have guidelines against doing that.

[Patrick Mary]

Thank you very much for your report.
This bug is now fixed in the current svn code line (commit #10536).