1. 25 Jul, 2019 1 commit
  2. 25 Jan, 2019 1 commit
  3. 11 Jan, 2019 1 commit
  4. 12 Dec, 2018 2 commits
  5. 05 Jul, 2018 1 commit
  6. 03 May, 2018 1 commit
  7. 16 Apr, 2018 1 commit
  8. 26 Feb, 2018 1 commit
  9. 08 Nov, 2017 1 commit
    • Christian Pfeiffer's avatar
      Restore exclusion of "gcc_eh" from implicit link libraries · 41aacca7
      Christian Pfeiffer authored
      Since commit v3.9.0-rc1~148^2 (Do not assume GCC libs are linked by all
      compilers, 2017-05-05) we no longer filter out all `gcc*` implicit link
      libraries.  This allows mixing of gcc and non-gcc compilers across
      languages.  However, this caused a subtle problem with how GCC makes
      exception handling symbols available to linked binaries.
      GCC (at least on MinGW) provides two different libraries with exception
      handling symbols:
      * gcc_s: A shared library with -fvisibility=default, used by -shared-libgcc.
      * gcc_eh: A static library with -fvisibility=hidden, used by -static-libgcc.
      The C compiler (on MinGW) defaults to -static-libgcc and uses gcc_eh.
      The C++ compiler defaults to -shared-libgcc and uses gcc_s when linking
      shared libraries and executables so that exceptions can propagate across
      shared libraries [1].  When linking a mixed-language binary, the C++
      compiler should be used along with its choice of gcc_s.  In this case
      gcc_eh should not be added even though the C compiler implies it because
      gcc_s supersedes it.
      Since the above-mentioned change, CMake is adding gcc_eh to C++ link
      lines that also contain C code on MinGW.  This causes both gcc_s and
      gcc_eh to be used, which is incorrect.  We can fix this simply by
      excluding gcc_eh from the C compiler's implicit link libraries.
      [1] https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Link-Options.html#Link-Options
      Fixes: #17436
  10. 23 Aug, 2017 1 commit
  11. 12 Jul, 2017 1 commit
  12. 05 Jun, 2017 1 commit
  13. 20 May, 2017 1 commit
    • Christian Pfeiffer's avatar
      ImplicitLinkInfo: Add support for PGI on Windows · c2c2d366
      Christian Pfeiffer authored
      Since PGI does not write linker directives into objects, the necessary
      libraries have to be parsed from commandline. PGI does however link the
      Visual C++ runtime libraries, so they have to be filtered out to ensure
      no collision with settings of other languages can occur.
  14. 05 May, 2017 1 commit
  15. 26 Apr, 2017 1 commit
  16. 03 Apr, 2017 2 commits
    • Brad King's avatar
      CMakeParseImplicitLinkInfo: Ignore ld -lto_library flag · 53f17333
      Brad King authored
      The `ld` tool in Xcode 8.3 now has a `-lto_library <path>` flag.  Ignore
      the flag instead of accidentally parsing it as `-l` with `to_library`.
      Fixes: #16766
    • Brad King's avatar
      Tests: Fix CMake.GetPrerequisites test config message · c2c22862
      Brad King authored
      Since commit v2.8.11~239^2~1 (ProcessorCount test: fix path to
      cmsysTestsCxx executable, 2013-01-24) we accidentally printed a literal
      `${CTEST_CONFIGURATION_TYPE}` instead of the actual build configuration.
      Update the message to use a generator expression to get the real build
      configuration used.
  17. 19 Feb, 2017 1 commit
  18. 10 Feb, 2017 1 commit
  19. 06 Feb, 2017 1 commit
    • Michael Maltese's avatar
      CMakeDetermineCompilerId: check with and without user-specified flags · 72ed051b
      Michael Maltese authored
      Clang may raise an error when passed a `-march=` option that doesn't
      correspond to the current target triple.  CMake cannot pass the target
      triple when determining the compiler id because it doesn't know how yet,
      but it does pass along user-specified flags.  This breaks when those
      user-specified flags include `-march=`.  Fix this use case by also
      trying to find the compiler id without the user-specified flags.
      Fixes: #16587
  20. 30 Jan, 2017 1 commit
    • Bernhard M. Wiedemann's avatar
      Tests: make tests pass with SOURCE_DATE_EPOCH set · 5181f1f8
      Bernhard M. Wiedemann authored
      Fix tests to account for commit 243aed52 (cmTimestamp: Support
      SOURCE_DATE_EPOCH to override current time, 2017-01-25).
      In openSUSE we are running the test-suite as part of the build and that
      failed in these two places when building everything with
      `SOURCE_DATE_EPOCH` set.
  21. 12 Jan, 2017 1 commit
  22. 10 Nov, 2016 2 commits
  23. 27 Sep, 2016 1 commit
  24. 12 Sep, 2016 1 commit
  25. 09 Aug, 2016 1 commit
  26. 27 Jul, 2016 1 commit
    • Daniel Pfeifer's avatar
      Use string(APPEND) in Tests · 7a649111
      Daniel Pfeifer authored
      Automate with:
      find Tests -type f -print0 | xargs -0 perl -i -0pe \
      's/set\(([a-zA-Z0-9_]+)(\s+)"\$\{\1\}([^"])/string(APPEND \1\2"\3/g'
  27. 11 Jul, 2016 1 commit
  28. 31 Mar, 2016 3 commits
  29. 18 Feb, 2016 1 commit
  30. 11 Sep, 2015 1 commit
    • 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.
  31. 14 Jul, 2015 1 commit
    • Brad King's avatar
      Tests: Move command failure cases into RunCMake infrastructure · e5ca59b4
      Brad King authored
      Move failure cases from the CMake.{If,List,While,GetProperty} tests over
      to the RunCMake.{if,list,while,get_property} tests to use the more
      modern infrastructure.  This also avoids using REGEX_ESCAPE_STRING to
      try to regex-match full paths.
  32. 14 May, 2015 1 commit
  33. 01 Apr, 2015 1 commit
    • Bill Newcomb's avatar
      Tests: Fix CMake.ELF test with read-only source (#15489) · a293dcb5
      Bill Newcomb authored
      When the cmake sources are all set to read-only (e.g. after importing
      into perforce), the CMake.ELF test fails because the copy of the binary
      is also read-only and cannot be modified.  Fix this by copying the
      binary without source permissions.
  34. 09 Mar, 2015 1 commit
    • Brad King's avatar
      Tests: Add more signature tests to RunCMake.configure_file test · 024e25e4
      Brad King authored
      Move the test cases from Tests/CMakeTests/ConfigureFileTest.cmake.in
      over to use the RunCMake.configure_file infrastructure.  This does much
      more robust verification of CMake output for each test case, and would
      have caught the regression fixed in our parent commit.
  35. 16 Dec, 2014 1 commit