1. 07 Jan, 2021 1 commit
    • Brad King's avatar
      ci: build separate macOS packages for macOS 10.13+ and macOS 10.10+ · 6410425e
      Brad King authored
      In order to support modern macOS features like Dark Mode, we need to use
      Qt 5.15, which requires macOS 10.13.  However, we still want to support
      macOS 10.10 as well, for which we need to use Qt 5.9.  Build separate
      macOS packages for these use cases.
      Fixes: #21606
      Issue: #20825
  2. 22 Dec, 2020 1 commit
  3. 14 Dec, 2020 1 commit
    • Robert Maynard's avatar
      ISPC: Generated Headers suffix configurable with a better default · c9a50f35
      Robert Maynard authored and Brad King's avatar Brad King committed
      The target property `ISPC_HEADER_SUFFIX` and associated global
      variable now can control the suffix used when generating the
      C/C++ interoperability ISPC headers.
      In addition the default suffix is now "_ispc.h" which matches the
      common convention that the ISPC compiler team uses and recommends.
  4. 10 Dec, 2020 2 commits
    • Brad King's avatar
      macOS: Offer control over host architecture on Apple Silicon hosts · 5f882f6c
      Brad King authored
      Since commit b6c60f14 (macOS: Default to arm64 architecture on Apple
      Silicon hosts, 2020-09-28, v3.19.0-rc1~63^2) we use `sysctl` to detect
      that we are running on Apple Silicon in a way that pierces Rosetta.
      This always sets `CMAKE_HOST_SYSTEM_PROCESSOR` to be `arm64` on such
      hosts.  However, macOS offers strong support for running processes under
      an emulated `x86_64` architecture.
      Teach CMake to select either `arm64` or `x86_64` as the host
      architecture on Apple Silicon based on the architecture of its own
      process.  When CMake is built as a universal binary, macOS will select
      whichever slice (architecture) is appropriate under the user's shell,
      and `CMAKE_HOST_SYSTEM_PROCESSOR` will match.
      Also offer a `CMAKE_APPLE_SILICON_PROCESSOR` variable and environment
      variable to provide users with explicit control over the host
      architecture selection regardless of CMake's own architecture.
      Finally, if `CMAKE_OSX_ARCHITECTURES` is not set, pass explicit flags to
      the toolchain to use selected host architecture instead of letting the
      toolchain pick.
      Fixes: #21554
    • Brad King's avatar
      ci: update macOS package to produce universal binaries · 56a075eb
      Brad King authored
      Update our deployment target to macOS 10.10.
      This is required by Qt 5.9.
      Fixes: #21565
      Issue: #20825
  5. 22 Nov, 2020 1 commit
    • Raul Tambre's avatar
      CUDA: Clang CUDA 11.1 support · 440dc98b
      Raul Tambre authored
      version.txt is gone from CUDA 11.1 installations, but the rest is the same.
      Instead of looking for version.txt look for <CUDA path>/nvvm/libdevice, which
      is the main thing that Clang requires (though it also checks for the existence
      of bin and include).
      Fixes #21353.
  6. 19 Nov, 2020 1 commit
    • Brad King's avatar
      Revert "specify language flag when source LANGUAGE property is set" · 30aa715f
      Brad King authored
      Revert commit 74b1c9fc (Explicitly specify language flag when source
      LANGUAGE property is set, 2020-06-01, v3.19.0-rc1~722^2) and the lookup
      tables from its two immediate ancestors.  The purpose of that change was
      to convert an explicit `LANGUAGE` source file property into an explicit
      language specification compiler flag like `-x c`.  This seems reasonable
      since the property is documented as meaning "indicate what programming
      language the source file is".  It is also needed to help compilers deal
      with non-standard source file extensions they don't recognize.
      However, some projects have been setting `LANGUAGE C` on `.S` assembler
      source files to mean "use the C compiler".  Passing `-x c` for them
      breaks the build because the `.S` sources are not written in C.  These
      projects should be updated to use `enable_language(ASM)`, for which
      CMake often chooses the C compiler as the assembler when using
      toolchains that support it (which would have to be the case for projects
      using the approach).
      Revert the change for now to preserve the old behavior for such projects.
      We can re-introduce it with a policy in a future version of CMake.
      Fixes: #21469
      Issue: #14516, #20716
  7. 03 Nov, 2020 1 commit
  8. 02 Nov, 2020 1 commit
  9. 24 Oct, 2020 1 commit
  10. 16 Oct, 2020 1 commit
  11. 12 Oct, 2020 1 commit
  12. 08 Oct, 2020 2 commits