1. 23 Jan, 2022 2 commits
    • Benjamin Morgan's avatar
      Explicitly use system VecCore in Jenkins builds · 44eaa5b6
      Benjamin Morgan authored
      Jenkins builds use an LCG view for build dependencies, which includes
      an install of VecCore. With the default being to use a system install
      on VecCore, the removal of the fallback to builtin does not change
      the behaviour here.
      
      Add BUILTIN_VECCORE=OFF to default build arguments to make this use
      case explicit.
      44eaa5b6
    • Benjamin Morgan's avatar
      Explicitly use builtin VecCore in GitLab CI · 0ae19239
      Benjamin Morgan authored
      GitLab CI setup assumed fallback to builtin VecCore as builds do
      not have an external install in their setups. This caused failures
      in CI following removal of fallback.
      
      Set BUILTIN_VECCORE to ON explicitly in build jobs on GitLab.
      0ae19239
  2. 22 Jan, 2022 2 commits
    • Benjamin Morgan's avatar
      Do not fallback to builtin VecCore if external not found · 011a39ab
      Benjamin Morgan authored
      Reported in VecGeom-583. We should not fallback to the builtin VecGeom
      option if use of external was requested but could not be found.
      
      Remove fallback to builtin VecGeom when external package requested and
      not found.
      
      Support switch between builtin/external in current build directory to
      ensure consistent builds.
      
      TODO: Use of FetchContent in CMake >= 3.11 is preferred, but VecCore
      does not support this well yet as it is not designed to be used as
      a subproject.
      011a39ab
    • Benjamin Morgan's avatar
      Remove obsolete local cmake_parse_arguments function · 1e787065
      Benjamin Morgan authored
      CMake has supplied cmake_parse_arguments natively since version 3.5.
      VecGeom's local implementation is both obsolete and can cause errors
      in the current cmake as it overrides the builtin.
      
      Remove the local implementation, relying on CMake's native support.
      1e787065
  3. 21 Jan, 2022 4 commits
  4. 07 Dec, 2021 1 commit
  5. 05 Nov, 2021 3 commits
  6. 28 Oct, 2021 1 commit
    • Benjamin Morgan's avatar
      Remove support for UMESIMD backend · 45e7180c
      Benjamin Morgan authored
      UMESIMD is no longer maintained and is known to have issues in testing
      with VecCore. VecCore and eventually native compiler, support for
      std::simd will render it obsolete.
      
      Remove UMESIMD from VecGeom's BACKEND option. Remove other
      use/references in C++ and configuration/CI code.
      45e7180c
  7. 26 Oct, 2021 4 commits
  8. 12 Oct, 2021 3 commits
  9. 06 Oct, 2021 9 commits
  10. 05 Oct, 2021 1 commit
  11. 02 Oct, 2021 4 commits
  12. 01 Oct, 2021 3 commits
  13. 29 Sep, 2021 1 commit
  14. 28 Sep, 2021 1 commit
  15. 27 Sep, 2021 1 commit
    • Benjamin Morgan's avatar
      Export required flags for VecGeom as compile options · 9016a352
      Benjamin Morgan authored
      Identified in upstream use by Geant4 - required compiler flags for
      using VecGeom (ISA and alignment) are not exported as CMake usage
      requirements for the imported targets. The client is required to use
      the CMake variables set in VecGeomConfig.cmake, and this may not be
      obvious or always done.
      
      Add the required flags to the VecGeom target as CMake compile options
      so they are propagated to clients linking the imported target.
      
      NB: These flags currently must be added to VecGeom's build-time
      CMAKE_CXX_FLAGS as well to support CUDA builds. This leads to repitition
      of the flags on the compile command line, but there should be no
      side effects as the flags used do not change behaviour when repeated.
      9016a352