1. 03 Aug, 2015 1 commit
    • Ben Boeckel's avatar
      hdf5: detect %I64d specifier · 71894112
      Ben Boeckel authored
      MSVC2015 has long long and uses I64 as the modifier. Other modifiers
      cause the standard library to throw up runtime errors and causes the
      test to fail.
  2. 30 Jul, 2015 1 commit
  3. 26 Jun, 2015 1 commit
    • Jean-Christophe Fillion-Robin's avatar
      Do not force manifest selection for vtkhdf5 libraries · e6e67374
      Jean-Christophe Fillion-Robin authored
      Following e16fac17, hdf5 libraries are build with -D_BIND_TO_CURRENT_VCLIBS_VERSION=1.
      When building VTK using VS2008, the result of this is that
      (1) VTK libraries all reference "9.0.21022.8" manifest expect the hdf5
      ones that reference "9.0.30729.1" and (2) in some case prevent application
      built against VTK from starting.
      The problem can also be detected when running CMakeVerifyManifest.cmake
      against the application install tree. It basically returns a message
      similar to the following one:
      ERROR: C:/Program Files/AwesomeApp 1.0.0/bin/vtkhdf5_hl-6.2.dll uses 9.0.30729.6161 not found in shipped manifests:[9.0.21022.8].
      CMake Error at C:/D/Support/cmake-3.2.2-win32-x86/share/cmake-3.2/Modules/CMakeVerifyManifest.cmake:118 (message):
        This distribution embeds dll versions that it does not ship, and may not
        work on other machines.
      Here are some more information copied from the convenience script allowing
      to patch the manifest from VS2008.
      Source:  https://gist.github.com/jcfr/3c7bef3f8b32f9f6ad4b
          Patch manifests in the redist folder of Visual Studio 9 (2008)
          To avoid the dll hell associated with runtime libraries distribution. There are
          two approaches:
           (1) edit the manifest file to have "9.0.21022.8" from the "9.0.30729.XXX" that is there, you "trick"
               your executable into using the newer dlls.  There appears to be no ill effects from this.
               The executables work, and you are using a newer version of the run time library.
           (2) add -D_BIND_TO_CURRENT_VCLIBS=1 to ALL files being compiled, then all of your executable files
               and dll files will refer to "9.0.30729.XXX" and you can use the redist files without any edits.
               However, you have to be careful here to recompile everything with this.  By default the compiler
               will build for "9.0.21022.8".
          This script will consider approach (1). If not already done, this script will first backup the
          manifest files and then patch them.
            * http://www.kitware.com/blog/home/post/4
            * http://stackoverflow.com/questions/8097733/how-to-distribute-c-run-time-crt-libraries
  4. 15 Jun, 2015 1 commit
  5. 16 Mar, 2015 1 commit
  6. 07 Feb, 2015 1 commit
  7. 26 Jan, 2015 1 commit
  8. 13 Jan, 2015 1 commit
    • Casey Goodlett's avatar
      Skip install of .pdb files for hdf5 on windows · 3c9e67a8
      Casey Goodlett authored
      This failed at least in configuration RelWithDebInfo due to a mismatch
      between the expected location of the .pdb file and the actual.  No
      other parts of VTK install the .pdb files, so removing the install of
      the hdf5 .pdb files for consistency.
      Change-Id: I0227678c9687cc9ff335653fb04784788b46fae3
  9. 09 Jan, 2015 1 commit
  10. 18 Dec, 2014 1 commit
  11. 12 Dec, 2014 1 commit
  12. 09 Dec, 2014 1 commit
  13. 08 Dec, 2014 1 commit
  14. 02 Dec, 2014 3 commits
  15. 01 Dec, 2014 2 commits
  16. 23 Nov, 2014 1 commit
  17. 21 Nov, 2014 1 commit
  18. 20 Nov, 2014 1 commit
  19. 19 Nov, 2014 1 commit
  20. 14 Nov, 2014 1 commit
  21. 29 Oct, 2014 1 commit
  22. 27 Oct, 2014 1 commit
  23. 14 Oct, 2014 1 commit
  24. 08 Sep, 2014 1 commit
    • Brad King's avatar
      ENH: Use if(DEFINED) to simplify conditions · 1f358017
      Brad King authored
      Replace old hacks of the form 'if("${VAR}" MATCHES "^${VAR}$")'
      with the much simpler 'if(NOT DEFINED ${VAR})'.
      Change-Id: I4dd42e9c3f5d03204992f5918650358eadc3734e
  25. 23 Jun, 2014 1 commit
  26. 11 Jun, 2014 1 commit
  27. 25 Apr, 2014 1 commit
    • Brad King's avatar
      Set MACOSX_RPATH property default consistently across CMake versions · cd0b6e68
      Brad King authored
      The MACOSX_RPATH target property was introduced in CMake 2.8.12, but we
      currently allow CMake 2.8.8.  Set CMAKE_MACOSX_RPATH to 0 by default
      so that we get consistent behavior across all versions of CMake.
      Leave a comment explaining when the default should be updated.
      Now that we set a MACOSX_RPATH default explicitly, we no longer need to
      set CMake Policy CMP0042 as was added in commit 2ad9f474 (Set CMake
      Policies CMP0025 and CMP0042 as necessary, 2014-03-11), so remove it.
      Change-Id: I8af24a728379176b9e7ab933206eaa956e1c60f2
  28. 11 Mar, 2014 2 commits
    • Brad King's avatar
      Set CMake Policies CMP0025 and CMP0042 as necessary · 2ad9f474
      Brad King authored
      CMake 3.0 introduces these policies to improve default behavior on OS X.
      Set them explicitly in VTK to avoid policy warnings.  VTK already works
      with the NEW behavior.
      Policy CMP0025 affects the project() command when the Apple Clang
      compiler is used so we need to set it in all the Examples.  Policy
      CMP0042 affects shared libraries on OS X, enabling MACOSX_RPATH by
      default.  Set it in directories where we create libraries.  Also tell
      KWSys to enable MACOSX_RPATH explicitly instead of setting the policy.
      Change-Id: I543b60ee1b8f629adb150e01ee83d99dddb66f46
    • Brad King's avatar
      vtkhdf5: Remove extra calls to cmake_minimum_required · ee1c7530
      Brad King authored
      Drop calls to this command in subdirectories.  They are never used as
      the top-level source directory.
      Change-Id: I6249719417ea8adb9297fab9f7e969c944bb3a13
  29. 10 Mar, 2014 1 commit
    • Brad King's avatar
      COMP: Drop invalid custom commands from HDF5 · 7df9a25f
      Brad King authored
      CMake 3.0 introduces policy CMP0040 to diagnose add_custom_command calls
      whose TARGET option names a target that does not exist.  Drop such
      unused custom commands from HDF5.
      Change-Id: Ic1fc58a3e2f171c35a9c055cdeca7bcc484ff837
  30. 14 Feb, 2014 1 commit
    • Bill Lorensen's avatar
      COMP: Remove bogus line info from generated files · 42415809
      Bill Lorensen authored
      The lex and yacc generated files retain some line preprocessor
      statements that contain non-existant filenames. These lines confuse
      newer version of lcov, the coverage tool.
      Change-Id: I3cbfd5b5583527d362cd80653f5fc4e970692bb1
  31. 18 Nov, 2013 1 commit
  32. 31 Jul, 2013 1 commit
    • Marcus D. Hanwell's avatar
      Removed the deprecated _CM24 CMake variables · 2f5fdb13
      Marcus D. Hanwell authored
      These were introduced for CMake 2.4 installation paths, and were
      deprecated in favor of VTK_INSTALL_*_DIR variables. Ported existing code
      to use these variables, removed the old declarations and removed some
      unused CMake code in Utilities/Release instead of porting it forward.
      Change-Id: I67ba95016eeb8536ebda8b8e44b30c9f2177744e
  33. 05 Jun, 2013 1 commit
    • Sven Buijssen's avatar
      Fix typos · 5ef33d3b
      Sven Buijssen authored
      Change-Id: I2edeb9e78066aa766e47ba37af92ddcbfe75a436
  34. 03 Feb, 2013 1 commit
    • David Cole's avatar
      BUG: Correct CMake message typos: FATAL -> FATAL_ERROR · 9e8594e1
      David Cole authored
      FATAL will just be emitted as message text, FATAL_ERROR
      actually triggers the intended "stop configuring now"
      Also, messge -> message.
      Most of these occurrences are luckily (?) in conditionals
      where they are rarely encountered in practice.
      Change-Id: I6a10bb6f7539e6c30d9cb1372570c697968226fe
  35. 28 Jan, 2013 1 commit
    • Utkarsh Ayachit's avatar
      Use newer variables for install rules. · cc89756d
      Utkarsh Ayachit authored
      Fixing install rules to use the newer VTK_INSTALL_RUNTIME_DIR,
      Change-Id: I362049561b3d4fa82a10d8176f4b4e387966e0de
  36. 05 Sep, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Fixing CMake Version requirements for OPTIONAL_COMPONENTS. · 5555ea69
      Utkarsh Ayachit authored
      Since OPTIONAL_COMPONENTS is only available in CMake 2.8.8 and greater, adding a
      check and treated OPTIONAL_COMPONENTS as REQUIRED COMPONENTS when using CMake
      version lesser than 2.8.8.
      Fixed a bug in the logic that was overwriting COMPONENTS when
      OPTIONAL_COMPONENTS were specified.
      Also fixes HDF5 to mark "C" as a required component.
      Change-Id: I76671b76125171e8d7a49e0774711076ce666531