1. 06 Apr, 2016 1 commit
  2. 08 Mar, 2016 1 commit
  3. 08 Jan, 2016 1 commit
  4. 23 Oct, 2015 1 commit
  5. 21 Oct, 2015 1 commit
    • Hans Johnson's avatar
      COMP: VTK and ITK H5 build program collision · 5720d26a
      Hans Johnson authored
      When both VTK and ITK are built with the same
      CMAKE_RUNTIME_OUTPUT_DIRECTORY settings, the H5detect and
      H5make_libsettings programs are generated by both VTK and ITK.  These
      are intended to be internal build configuration programs that determine
      the capabilities of the local compiler and OS.
      When VTK and ITK diverge in their version of HDF5, conficts occur that
      cause difficult to debug compiler errors.
      By adding a prefix here the program name conflict can be avoided.
  6. 26 Sep, 2015 1 commit
  7. 03 Aug, 2015 2 commits
    • Ben Boeckel's avatar
      hdf5: fix long long format detection · a4cf06de
      Ben Boeckel authored
      The code does a loop itself, so just run it once and use its output as
      the result.
      In fact, this code would always return "ll" because if the file had a
      right answer, it would return 0 for it, but then think it was "ll" that
      passed, not one of the formats in the file.
    • 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.
  8. 30 Jul, 2015 1 commit
  9. 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
  10. 15 Jun, 2015 1 commit
  11. 16 Mar, 2015 1 commit
  12. 07 Feb, 2015 1 commit
  13. 26 Jan, 2015 1 commit
  14. 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
  15. 09 Jan, 2015 1 commit
  16. 18 Dec, 2014 1 commit
  17. 12 Dec, 2014 1 commit
  18. 09 Dec, 2014 1 commit
  19. 08 Dec, 2014 1 commit
  20. 02 Dec, 2014 3 commits
  21. 01 Dec, 2014 2 commits
  22. 23 Nov, 2014 1 commit
  23. 21 Nov, 2014 1 commit
  24. 20 Nov, 2014 1 commit
  25. 19 Nov, 2014 1 commit
  26. 14 Nov, 2014 1 commit
  27. 29 Oct, 2014 1 commit
  28. 27 Oct, 2014 1 commit
  29. 14 Oct, 2014 1 commit
  30. 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
  31. 23 Jun, 2014 1 commit
  32. 11 Jun, 2014 1 commit
  33. 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
  34. 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
  35. 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