1. 03 Jan, 2018 1 commit
  2. 15 Dec, 2017 2 commits
  3. 08 Nov, 2017 1 commit
  4. 23 Oct, 2017 1 commit
  5. 03 Oct, 2017 1 commit
  6. 02 Oct, 2017 2 commits
  7. 20 Sep, 2017 1 commit
    • Kenneth Moreland's avatar
      Update copyright for Sandia · c3a3184d
      Kenneth Moreland authored
      Sandia National Laboratories recently changed management from the
      Sandia Corporation to the National Technology & Engineering Solutions
      of Sandia, LLC (NTESS). The copyright statements need to be updated
  8. 28 Aug, 2017 3 commits
  9. 10 Aug, 2017 1 commit
    • Robert Maynard's avatar
      VTK-m now provides a default and a list of types for CMAKE_BUILD_TYPE. · ad3e0f32
      Robert Maynard authored
      CMake has several default build types, but if nothing is specified when
      configuring your project it defaults to an empty string and no optimization
      flags are used.
      It will now default to using a debug build if the source directory is a git
      clone, or a release build if not. Additionally when using ccmake or cmake-gui
      this will provide a nice list of possible options for CMAKE_BUILD_TYPE.
  10. 31 Jul, 2017 1 commit
  11. 24 May, 2017 1 commit
  12. 27 Jan, 2017 1 commit
  13. 26 Jan, 2017 1 commit
  14. 18 Jan, 2017 1 commit
  15. 16 Jan, 2017 1 commit
  16. 21 Oct, 2016 1 commit
  17. 03 Oct, 2016 4 commits
    • Kenneth Moreland's avatar
      Fix some issues with OpenGL configuration · 039efd6b
      Kenneth Moreland authored
      Change the OpenGL configuration to require GLEW as most of the OpenGL
      code actually requires GLEW (or will as soon as the VBO branch gets
      merged in).
      Also removed some stray find_package commands and rearranged the
      configuration to use the vtkm_configure_component_* commands instead.
    • Kenneth Moreland's avatar
      Install supporting Find*.cmake files · 6c511c86
      Kenneth Moreland authored
      The vtkm/CMake directory has several Find*.cmake configuration files
      that were used both by the base VTK-m configuration as well as
      configuration of projects that use VTK-m. However, several of these
      files (particularly the newer ones) were not installed. This change
      fixes that.
    • Kenneth Moreland's avatar
      Change VTKmDetectCUDAVersion install extension · fffefe22
      Kenneth Moreland authored
      The VTKmDetectCUDAVersion.cxx source file used during configuration to
      detect the native version of CUDA hardware was renamed to
      VTKmDetectCUDAVersion.cu. However, the old filename was still trying to
      be installed, which caused the install target to fail.
    • Kenneth Moreland's avatar
      Drop cxx_constexpr from target compile features · 13534a06
      Kenneth Moreland authored
      It turns out, this is not supported on MSVC 2013. Presumably
      cxx_auto_type is sufficient to force C++11 on all supported compilers.
  18. 29 Sep, 2016 1 commit
    • Kenneth Moreland's avatar
      Add C++11 flags to sub-projects · 9f0bd788
      Kenneth Moreland authored
      Recently VTK-m was changed to require C++11. The internal builds set
      properties to require C++11, but these never make it to the
      configuration for projects that use the VTK-m package (i.e. not declared
      in VTKmConfig.cmake).
      This change adds a new CMake target, vtkm, which is an interface. It
      does not point to an actual library, but it allows code that links it in
      to have the appropriate compile flags.
  19. 21 Sep, 2016 2 commits
  20. 09 Sep, 2016 1 commit
  21. 07 Sep, 2016 4 commits
    • Kenneth Moreland's avatar
      Fix issue where exports failed when no libraries · 434f5419
      Kenneth Moreland authored
      Currently, the only library created is for the rendering package. If
      VTKm_BUILD_RENDERING is off, then no libraries are created. If no
      libraries are created, then there is nothing that declares a VTKmTargets
      export. If there is nothing that creates a VTKmTargets export, the
      export command fails.
      Aaarg!!!! I can't even find a way to query whether an export is valid
      (in the same way you can query whether a target exists). I added a
      global variable that recorded whether vtkm_library added a library
      (where things are added to the VTKmTargets export). The export command
      is called if any libraries were created, a stub is created and installed
    • Kenneth Moreland's avatar
      Add target exports to installed files · 74aeeaa6
      Kenneth Moreland authored
      This makes it much easier for dependent CMake projects to find the VTK-m
    • Kenneth Moreland's avatar
      Enable building shared libraries · 7e0ec48c
      Kenneth Moreland authored
    • Kenneth Moreland's avatar
      Create configuration for rendering library · ea8602d8
      Kenneth Moreland authored
      I have noticed at least on my windows machine that source code that uses
      the rendering package is taking a long time to compile. The rendering
      library does not rely much on templates and more on virtual methods.
      Thus, it is a good candidate for moving to a library so that it need be
      compiled only once.
      This sets up the configure scripts to create the library. There is also
      a simple port of one class to the library. More will follow.
  22. 01 Sep, 2016 1 commit
  23. 29 Aug, 2016 1 commit
    • Kenneth Moreland's avatar
      Honor CMake policy CMP0058 · e4ca73fc
      Kenneth Moreland authored
      CMake policy CMP0058, introduced in CMake 3.3, requires that all
      intermediate files created during the build process will be declared as
      an output or byproduct of a target. See "cmake --help-policy CMP0058"
      for details.
      Per this policy, CMake was giving a warning about some files generated
      during configuration (e.g. with configure_file) because they were files
      in the build directory with no apparent target command. This is not an
      issue since the configure will ensure that the file is always there
      before the build starts. Thus, we declare that we will adhere to the new
      policy to avoid the warning.
  24. 24 Aug, 2016 1 commit
  25. 23 Aug, 2016 2 commits
    • Kenneth Moreland's avatar
      Configure examples after writing VTKmConfig.cmake · ab528b8e
      Kenneth Moreland authored
      The examples configuration now behave like external projects and use
      find_package to configure themselves. As such that file should be built
      before we try to configure the examples.
    • Kenneth Moreland's avatar
      Fix config issues with headers and libraries · 866c617c
      Kenneth Moreland authored
      There were a couple of places where the configure scripts did not add
      either includes to VTKm_INCLUDE_DIRS or libraries to VTKm_LIBRARIES.
      The biggest offender was when the examples used find_package to load the
      VTK-m configuration it needed. find_package cleared out the includes and
      libraries, but it did not clear out the VTKm_<COMPONENT>_FOUND
      variables. Normally, these variables would not be set before
      find_package is called, but in this case the examples were called after
      some partial configuration. I got around this issue by clearing out all
      the *_FOUND variables in VTKmConfig.cmake.
  26. 03 Aug, 2016 1 commit
  27. 28 Jul, 2016 1 commit
  28. 25 Jul, 2016 1 commit