1. 30 Sep, 2015 1 commit
    • Brad King's avatar
      Disable shared library support when compiler links statically · 8b4873a1
      Brad King authored
      When a user or a compiler wrapper adds '-static' to the compiler flags
      then it will always link static binaries.  Detect this from the compiler
      id binary and disable TARGET_SUPPORTS_SHARED_LIBS.  This will prevent
      projects from accidentally adding shared libraries when the toolchain
      does not support them.  It also helps CMake avoid linking with flags
      that require shared libraries to be supported.
  2. 28 Sep, 2015 1 commit
  3. 25 Sep, 2015 5 commits
  4. 22 Sep, 2015 1 commit
    • Stephen Kelly's avatar
      Project: Don't require computed default dialect if compiler was forced. · d1375851
      Stephen Kelly authored
      Commit 7235334a (Project: Determine default language dialect for the
      compiler., 2015-09-15) introduced a mechanism to determine the default
      dialect used for the running compiler.  If conditions in
      the <CompilerId>-<Lang>.cmake file are such that compile features for
      that version of the compiler should be supported, the _DEFAULT_STANDARD
      is set to the computed value.
      However, the CMakeForceCompiler module allows users to bypass execution of the
      compiler by CMake.  In that case, do not set the _DEFAULT_STANDARD variable at
      all, which effectively disables the compile-features where the module is used.
      No compile features have ever been recorded where the module is used so no
      functionality is lost.
  5. 21 Sep, 2015 2 commits
  6. 20 Sep, 2015 1 commit
    • Roman Donchenko's avatar
      Introduction of CPACK_VERBATIM_VARIABLES variable · bc2e54db
      Roman Donchenko authored
      If variable is set to TRUE, values of all variables prefixed with CPACK_
      will be escaped so special characters such as dolar sign, quotes or
      foreward slash will not be lost. By default variable is treated as set
      to FALSE for back compatibility.
      The cpack_encode_variables macro is changed into a function to remove
      scope pollution. There should be no other effects.
  7. 18 Sep, 2015 4 commits
  8. 17 Sep, 2015 9 commits
  9. 16 Sep, 2015 4 commits
  10. 15 Sep, 2015 1 commit
  11. 11 Sep, 2015 2 commits
    • Paul Romano's avatar
      FindHDF5: Add NAMES_PER_DIR and introduce HDF5_PREFER_PARALLEL · fd26a19a
      Paul Romano authored
      The calls to find_program now use NAMES_PER_DIR so that the first executable
      (e.g. h5pcc) appearing on their PATH will get chosen. The HDF5_PREFER_PARALLEL
      variable swaps the search order when it is set to true in the event that a
      directory being search contains both h5cc and h5pcc.
    • Brad King's avatar
      CMakeParseImplicitLinkInfo: Do not match "VAR=..." as link line (#15737) · 97ffbcd8
      Brad King authored
      When compiling with
        LDFLAGS='-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
      the compiler output includes a line like
        COLLECT_GCC_OPTIONS='-specs=/usr/lib/rpm/redhat/redhat-hardened-ld' ...
      that our link line regex matches due to an argument ending in "-ld".
      Since it is not really the link line no implicit link information is
      dectected.  Exclude "VAR=..." lines from consideration as link lines to
      fix this.
  12. 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.
  13. 09 Sep, 2015 8 commits