1. 29 Oct, 2009 1 commit
    • Brad King's avatar
      ENH: Install VTK package version file for find_package · 19852427
      Brad King authored
      We teach VTK to install a package version file 'VTKConfigVersion.cmake'
      next to the package config file 'VTKConfig.cmake'.  This allows code
      like
      
        find_package(VTK 5.5)
      
      in user projects to find only compatible VTK versions.  Enforcement of
      the version check will only work when the user project runs with the
      FindVTK.cmake module from CMake 2.8 or higher.  The package version file
      will simply be ignored by older CMake versions.
      19852427
  2. 21 Oct, 2008 2 commits
  3. 17 Sep, 2008 2 commits
  4. 06 Feb, 2007 2 commits
  5. 04 Oct, 2006 1 commit
  6. 05 Sep, 2006 1 commit
  7. 04 May, 2006 1 commit
  8. 23 Mar, 2006 1 commit
  9. 09 Mar, 2006 1 commit
  10. 28 Feb, 2006 1 commit
  11. 25 Feb, 2006 1 commit
  12. 19 Feb, 2006 2 commits
  13. 13 Feb, 2006 2 commits
  14. 21 Dec, 2005 1 commit
  15. 15 Dec, 2005 1 commit
  16. 14 Dec, 2005 1 commit
  17. 10 Dec, 2005 1 commit
    • Sebastien Barre's avatar
      ENH: The VTK_TK_RESOURCE_FILE file was not exported properly in the... · c7c81de8
      Sebastien Barre authored
      ENH: The VTK_TK_RESOURCE_FILE file was not exported properly in the VTKConfig.cmake file for the install tree. No reason to since nothing was installed, but now that I fixed the installation part, I also fixed it that variable for VTKConfig.cmake.in.
      
      While I was at it, I fixed the VTK_TCL_SUPPORT_LIBRARY_PATH and VTK_TK_SUPPORT_LIBRARY_PATH that were not exported properly in the VTKConfig.cmake file for the install tree. Both variables point to a place where the Tcl/Tk *support* files can be found. The support files are a bunch of Tcl scripts that are read at initialization time by Tcl/Tk, and provide functionalities that were not coded in C in the Tcl/Tk library but directly in Tk. The support files also including encoding table and other stuff. This is a source of many problems, but yes, they have to be read at run-time. So the deal is, if you build the vtk.exe shell against a Tcl/Tk static, and try to run it, it fails, because it tries to find the support files *relative* to its position. When linked against Tcl/tk DLLs, this works magically, the support files are found relative to the DLLs. So what we have to do, for vtk.exe, as well as PV, VV, VJ, is copy the support files from the Tcl/tk source tree, to a location in our build tree *and* install tree. This part was done properly, but VTK_TCL_SUPPORT_LIBRARY_PATH and VTK_TK_SUPPORT_LIBRARY_PATH were not pointing to the *installed* support files in the installed VTKConfig.cmake. So if you were to distribute VTK in a static form, KWWidgets would not find where to copy the support files from, even though they were available in the VTK tree. I fixed that.
      c7c81de8
  18. 07 Dec, 2005 2 commits
  19. 31 Aug, 2005 1 commit
  20. 23 Aug, 2005 1 commit
  21. 21 Aug, 2005 1 commit
  22. 11 Aug, 2005 1 commit
    • Brad King's avatar
      ENH: Re-organizing the VTK installation. Libraries are now installed in... · eefd79d9
      Brad King authored
      ENH: Re-organizing the VTK installation.  Libraries are now installed in PREFIX/lib instead of PREFIX/lib/vtk.  This is now safe because they have version numbers on UNIX.  The Tcl package is now installed in PREFIX/lib/vtk-<version> so that it can be automatically found by the vtk or tclsh executables without setting TCLLIBPATH.  The CMake packaging files for VTK are also installed in PREFIX/lib/vtk-<version>, but this location can be separately configured.  The Doxygen files install location can now also be configured separately.
      eefd79d9
  23. 30 Jun, 2005 1 commit
  24. 22 Jun, 2005 1 commit
  25. 02 May, 2005 1 commit
  26. 01 Mar, 2005 1 commit
    • Brad King's avatar
      ENH: Using variables VTK_INSTALL_BIN_DIR, VTK_INSTALL_LIB_DIR, and... · 0237f1dc
      Brad King authored
      ENH: Using variables VTK_INSTALL_BIN_DIR, VTK_INSTALL_LIB_DIR, and VTK_INSTALL_INCLUDE_DIR for install locations.  They default to the old values (/bin, /lib/vtk, and /include/vtk) but can be changed by parent projects like ParaView to install inner VTK instances in a special location.
      0237f1dc
  27. 04 Feb, 2005 1 commit
  28. 11 Jan, 2005 1 commit
  29. 01 Oct, 2004 1 commit
  30. 30 Sep, 2004 1 commit
  31. 02 Sep, 2004 1 commit
  32. 15 Mar, 2004 1 commit
  33. 12 Mar, 2004 1 commit
  34. 08 Jan, 2004 1 commit