1. 13 May, 2019 1 commit
  2. 02 May, 2019 1 commit
  3. 29 Apr, 2019 1 commit
  4. 11 Apr, 2019 1 commit
  5. 12 Jul, 2018 1 commit
  6. 27 Jan, 2018 1 commit
  7. 30 May, 2017 1 commit
  8. 26 May, 2017 1 commit
  9. 02 May, 2017 1 commit
  10. 02 Dec, 2016 1 commit
    • Brad King's avatar
      Features: Make feature recording conditions more consistent · 684e4d20
      Brad King authored
      Condition all calls to `_record_compiler_features_{c,cxx}` on
      `_result EQUAL 0` so that adding new language standards later does
      not need to update them.  Avoid some duplicate compiler version
      checks by conditioning C11 and CXX14 feature recording on the
      existence of `CMAKE_{C11,CXX14}_STANDARD_COMPILE_OPTION` (whose
      setting already used the version check).
      684e4d20
  11. 10 Nov, 2016 1 commit
  12. 02 Nov, 2016 1 commit
  13. 27 Oct, 2016 2 commits
    • Brad King's avatar
      Features: Record features for Intel Compiler on Windows · 369d5809
      Brad King authored
      Since this compiler always defines `__cplusplus` to `1` we need to use
      `_MSC_VER`, `__INTEL_CXX11_MODE__`, and the feature test macro named
      `__cpp_aggregate_nsdmi` to detect C++11 and C++14 modes.
      
      With no `-Qstd=` flag this compiler defaults to C++98 plus a subset of
      C++11/C++14 features needed to be compatible with MSVC.  We pretend it
      is plain C++98 and add a `-Qstd=` flag whenever needed for C++11 or
      above features even if they would happen to be available in MSVC-mode.
      
      Closes: #16384
      369d5809
    • Brad King's avatar
      Intel: Remove incorrect C++98 standard compiler flag on Windows · 967dcf36
      Brad King authored
      The change in commit 05e05cd2 (Intel: Fix compiler C++98 standard flag
      on Windows, 2016-10-26) was wrong.  The Intel C++ Compiler for Windows
      does not support either `-Qstd=c++98` or `-Qstd=gnu++98`.  Simply remove
      both flags for this compiler and use no options at all to achieve this
      mode.
      
      Issue: #16384
      967dcf36
  14. 26 Oct, 2016 1 commit
  15. 24 Oct, 2016 1 commit
    • Brad King's avatar
      Intel: Fix compiler extension flags on Windows · 881585f9
      Brad King authored
      The extension flags enabled by commit v3.6.0-rc1~120^2~1 (Features:
      Record standard flags for Intel C/C++ on Windows, 2016-04-18) of the
      form `-Qstd=gnu++11` are not supported by the Intel C/C++ Compiler for
      Windows.  Fall back to using the non-extension form of the flags.
      
      Issue: #16384
      881585f9
  16. 05 Jul, 2016 1 commit
    • Brad King's avatar
      Intel: Do not use GNU-like flags on Windows · f9dbe22c
      Brad King authored
      Refactor options out of `Modules/Compiler/Intel-{ASM,C,CXX,Fortran}.cmake`
      into a common helper in `Modules/Compiler/Intel.cmake`.  Condition
      them to be used only on non-Windows hosts where the Intel compiler
      is GNU-like instead of MSVC-like.
      
      Previously this worked only because the options were later overridden
      by `Modules/Platform/Windows-Intel*.cmake`, but it is cleaner to not
      set the options in the first place.
      f9dbe22c
  17. 28 Apr, 2016 2 commits
  18. 15 Mar, 2016 1 commit
  19. 13 Jul, 2015 1 commit
    • Brad King's avatar
      Factor an <INCLUDES> placeholder out of <FLAGS> in rule variables · c736de7b
      Brad King authored
      Teach the Makefile and Ninja generators to substitute for an <INCLUDES>
      placeholder instead of putting -I in <FLAGS>.  Update our values for
      
        CMAKE_<LANG>_COMPILE_OBJECT,
        CMAKE_<LANG>_CREATE_ASSEMBLY_SOURCE, and
        CMAKE_<LANG>_CREATE_PREPROCESSED_SOURCE
      
      to place <INCLUDES> just before <FLAGS>.
      c736de7b
  20. 07 Feb, 2014 1 commit
  21. 04 Nov, 2013 1 commit
  22. 02 Jun, 2013 1 commit
  23. 15 Aug, 2012 1 commit
  24. 13 Aug, 2012 1 commit
    • Kitware Robot's avatar
      Convert CMake-language commands to lower case · 77543bde
      Kitware Robot authored
      Ancient CMake versions required upper-case commands.  Later command
      names became case-insensitive.  Now the preferred style is lower-case.
      
      Run the following shell code:
      
      cmake --help-command-list |
      grep -v "cmake version" |
      while read c; do
          echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
      77543bde
  25. 19 Sep, 2009 1 commit
  26. 01 Sep, 2009 1 commit
    • Brad King's avatar
      Use Intel for Linux flags only on Linux · 2eca4dd2
      Brad King authored
      The commit "Split Intel compiler information files" moved some Linux
      specific flags into the platform-independent Intel compiler info files.
      This moves them back.
      2eca4dd2
  27. 21 Aug, 2009 1 commit
    • Brad King's avatar
      Split Intel compiler information files · 2ce6a7d0
      Brad King authored
      This moves platform-independent Intel compiler flags into separate
      "Compiler/Intel-<lang>.cmake" modules.  Platform-specific flags are
      left untouched.
      2ce6a7d0
  28. 29 Jul, 2009 1 commit
  29. 23 Jul, 2009 1 commit
    • Brad King's avatar
      ENH: Implicit link info for C, CXX, and Fortran · 07ea19ad
      Brad King authored
      This teaches CMake to detect implicit link information for C, C++, and
      Fortran compilers.  We detect the implicit linker search directories and
      implicit linker options for UNIX-like environments using verbose output
      from compiler front-ends.  We store results in new variables called
      
        CMAKE_<LANG>_IMPLICIT_LINK_LIBRARIES
        CMAKE_<LANG>_IMPLICIT_LINK_DIRECTORIES
      
      The implicit libraries can contain linker flags as well as library
      names.
      07ea19ad