- Add patch to make the port build GCC and CMake 3.1.0.

  Tulip overrides CMake's built-in add_library() and add_executable()
  commands, so obviously things would explode at some point.

  This is a band-aid solution to get things working; the right solution
  would be to stop overriding CMake's commands, or even stopping setting
  RPATH on libraries and executables altogether, but that depends on getting
  the Tulip developers involved (I'm still figuring out if they respond to
  pings and patches).

- Use quazip from ports instead of building Tulip's bundled copy. Bundled
  software is evil.

- Clean up CMAKE_ARGS. PYTHON_INCLUDEDIR and LOCALBASE were used years ago
  in patch-CMakeLists.txt, but that has not been the case for several
  releases at least.

- Clean up the port's dependencies:
  * devel/qt4-assistant, devel/qt4-designer have not been required since
    Tulip 3.something.
  * devel/qt4-libqtassistantclient is severely outdated and unsupported,
    thankfully it has not been used since Tulip 3.4.0.
  * devel/libqxt is not needed because Tulip always builds its own bundled
    copy.
  * Add explicit dependency on print/freetype2 since the port links directly
    against it.
  * Stop depending on devel/libexecinfo directly and use USES=execinfo
    instead.

0 files changed, 0 insertions, 0 deletions