1. 09 Jul, 2019 1 commit
    • Alex Turbov's avatar
      Refactor: Move CPack internal files to `Internal/CPack/` directory · 98617f1b
      Alex Turbov authored
      Some commits ago all CPack internal `*.cmake` files have been moved
      to `Internal/CPack/`. This commit also move some templates
      internally used by generators to the same location to make
      `Modules/` directory less noisy w/ files the end users don't
      need to use/see.
  2. 12 Jun, 2019 1 commit
    • Kyle Edwards's avatar
      CPack: Fix SONAME regex in DEB generator · 3092c27f
      Kyle Edwards authored
      The DEB generator was written to parse output from GNU readelf.
      However, LLVM's readelf has a slightly different output format,
      without parentheses around the word "SONAME". Update the regex to
      account for this difference.
      Fixes: #19362
  3. 05 Jun, 2019 1 commit
  4. 30 Apr, 2019 1 commit
  5. 09 Apr, 2019 1 commit
  6. 27 Mar, 2019 1 commit
  7. 20 Mar, 2019 1 commit
  8. 25 Feb, 2019 1 commit
  9. 19 Dec, 2018 1 commit
  10. 28 Nov, 2018 1 commit
  11. 11 Nov, 2018 1 commit
  12. 05 Nov, 2018 1 commit
    • Craig Scott's avatar
      CPack: Rename Ext generator to External · 20d5e77a
      Craig Scott authored
      Ext and External were used inconsistently in the code and the
      docs. This change converts all uses of Ext to External, including
      within variable names used by the generator.
  13. 03 Oct, 2018 1 commit
    • luz.paz's avatar
      Fix misc. typos · 6b4c5a03
      luz.paz authored
      Found via `codespell -q 3 -I ../cmake-whitelist.txt --skip="./Utilities"`
      where the whitelist consists of
  14. 21 Sep, 2018 1 commit
  15. 18 Sep, 2018 1 commit
  16. 12 Sep, 2018 1 commit
  17. 02 Jul, 2018 1 commit
    • Kyle Edwards's avatar
      CPack: Add "CPack External" generator · 80914d88
      Kyle Edwards authored
      This generator doesn't actually package the files. Instead, it
      provides a metadata JSON file that can be used by external packaging
      software to do its own packaging. This JSON file provides information
      about the components, component groups, installation types, and CMake
  18. 26 Jun, 2018 1 commit
    • Daniel Wyatt's avatar
      CPack/RPM: Use CMAKE_COMMAND to reference cmake executable · 611ad194
      Daniel Wyatt authored
      Ensure we use the `cmake` corresponding to the running `cpack`
      even if it is not first in `PATH` or has had its name changed.
      This was accidentally left out in commit v3.7.0-rc1~81^2 (CPack/RPM:
      Generate source rpm (SRPM) packages on demand, 2016-09-19).
  19. 21 Jun, 2018 1 commit
    • Kyle Edwards's avatar
      CPack: Move internal implementation modules into Internal/CPack directory · 48bc8b2b
      Kyle Edwards authored
      These modules are not meant to be included by user code, they are
      only an internal implementation detail for CPack. Having them live
      in the main Modules directory with documentation was misleading, so
      they have been moved into Modules/Internal/CPack, and their
      documentation has been stripped following its move into the new
      "CPack Generators" section. No-op modules which contained only
      documentation have been removed entirely.
      The only module that hasn't been moved is CPackIFW, because it
      contains user-facing macros which would be lost if it were moved.
      So, the CPackIFW module has been updated with a note explaining what
      needs to (eventually) happen.
  20. 09 May, 2017 1 commit
    • Brad King's avatar
      Features: On SunPro link feature check with lang std flag · d49aa107
      Brad King authored
      Follow up commit e17b1791 (Features: On SunPro link with language
      standard compiler flag, 2017-04-28) to apply the same fix to the feature
      checks.  The `try_compile` used for these is intentionally not using
      `CXX_STANDARD`-based logic so that it can test the individual flags.
  21. 02 Nov, 2016 2 commits
    • Brad King's avatar
      Features: Add meta-features requesting awareness of a particular standard · b0996a3f
      Brad King authored
      A common use case of `target_compile_features` is simply to specify that
      the compiler should be run in a mode that is aware of e.g. C++11.  Some
      projects simply specify a particular C++11-only feature to request this.
      Provide a first-class way to do this by naming features after the
      corresponding language standard.  Record them as always available in the
      corresponding standard level so that requesting them always ensures that
      standard (or higher) is used.
    • Brad King's avatar
      Features: Centralize per-compiler recording macros · 8b6cc251
      Brad King authored
      Simplify and de-duplicate per-compiler feature recording macros and
      convert to a centralized per-language macro.
  22. 10 Sep, 2015 1 commit
    • Brad King's avatar
      Features: Extract strings from test binary more reliably (#15736) · 150e1b27
      Brad King authored
      Since commit v3.1.0-rc1~635^2~7 (project: Add infrastructure for
      recording CXX compiler features, 2013-10-17) we compile a test source to
      a binary and then extract "<LANG>_FEATURES:..." strings from the binary
      with the file(STRINGS) command.  Add a newline at the beginning of the
      string literal to be sure file(STRINGS) can extract the first entry as a
      string independent of whatever else the compiler may put before the
      storage it allocates for the literal within the binary.
  23. 15 May, 2014 1 commit
    • Stephen Kelly's avatar
      Features: Use the features symbol in the feature-test compile. · f6f10954
      Stephen Kelly authored
      Clang discards the entire string if it is not used, removing
      the ability to read the features from the compiled binary. That
      is prevented by using the symbol.
      GNU with -O3 also discards the string, so use the string in a
      way which is determined by a runtime value (argc) to prevent
      it being discarded.
  24. 07 May, 2014 2 commits
  25. 02 May, 2014 1 commit
  26. 07 Apr, 2014 1 commit
    • Stephen Kelly's avatar
      project: Add infrastructure for recording CXX compiler features · faeddf64
      Stephen Kelly authored
      Add a feature test using the compiler macros and the preprocessor to
      determine available features.
      Add a CMAKE_CXX_COMPILE_FEATURES variable which contains all features
      known to the loaded compiler, and a CMAKE_CXX_KNOWN_FEATURES variable
      containing all features known to CMake.  Add language standard specific
      variables for internal use to determine the standard-specific compile
      flags to use.
      This will be extended to other languages in the future.  Follow-up
      commits will add features which will be recorded by the feature test.