1. 15 Apr, 2016 2 commits
  2. 11 Apr, 2016 1 commit
  3. 31 Jul, 2015 1 commit
    • Brad King's avatar
      FindMPI: Drop unnecessary and incorrect use of GetPrerequisites · 1c46b6ae
      Brad King authored
      Since commit v2.8.5~121^2~2 (FindMPI: Handle multiple languages,
      2010-12-29) we called the GetPrerequisites is_file_executable function
      but passed the name of a CMake variable instead of its value.  Therefore
      the function has always failed and caused the search for the compiler
      name to run even with an absolute path.  Switch to using if(IS_ABSOLUTE)
      instead and drop use of GetPrerequisites.
      1c46b6ae
  4. 10 Jul, 2015 1 commit
  5. 14 Jan, 2015 1 commit
    • Ben Boeckel's avatar
      FindMPI: handle trailing slash from $MSMPI_BIN · 68857ccd
      Ben Boeckel authored
      When installing, MSMPI puts a trailing backslash in the MSMPI_BIN
      environment variable. This causes trouble when concatenating in CMake
      since the list separator is now escaped and no longer a list separator
      due to the trailing backslash. Instead, use file(TO_CMAKE_PATH) to make
      the path CMake-friendly.
      68857ccd
  6. 06 Jan, 2015 2 commits
  7. 12 Dec, 2014 1 commit
  8. 11 Dec, 2014 1 commit
  9. 04 Dec, 2014 2 commits
  10. 20 Oct, 2014 1 commit
    • Ben Boeckel's avatar
      Avoid if() quoted auto-dereference · 29c3edb8
      Ben Boeckel authored
      When testing CMAKE_<LANG>_COMPILER_ID values, do not explicitly
      dereference or quote the variable. We want if() to auto-dereference the
      variable and not its value. Also replace MATCHES with STREQUAL where
      equivalent.
      29c3edb8
  11. 11 Aug, 2014 1 commit
    • Marcel Loose's avatar
      FindMPI: Honor MPI_HOME for MPIEXEC (#14347) · 150c2125
      Marcel Loose authored
      We already use MPI_HOME and ENV{MPI_HOME} as hints for the location
      of the MPI compilers.  Do the same for mpiexec, and then use the
      location of mpiexec as a hint to find the compilers.
      150c2125
  12. 14 Apr, 2014 1 commit
  13. 11 Apr, 2014 1 commit
  14. 15 Oct, 2013 1 commit
  15. 07 May, 2013 1 commit
  16. 04 Nov, 2012 1 commit
  17. 27 Sep, 2012 1 commit
    • David Cole's avatar
      FindMPI: Set correct variables for calls to FPHSA · 8b7a5c61
      David Cole authored
      Since FPHSA is called for multiple compiler languages with "MPI_${lang}"
      rather than just "MPI", make sure variables for controlling QUIET,
      REQUIRED and VERSION are propagated with names prefixed by MPI_${lang}
      as well, rather than just MPI.
      
      The find_package call sets up the values of MPI_FIND_REQUIRED and friends,
      but these calls to FPHSA need MPI_${lang}_FIND_REQUIRED and friends in
      order to function as intended.
      8b7a5c61
  18. 20 Mar, 2012 1 commit
  19. 16 Jan, 2012 1 commit
  20. 21 Jun, 2011 2 commits
    • Todd Gamblin's avatar
      Fix issues with removing try_compile input file. · 8756e77f
      Todd Gamblin authored
      - Don't remove input file
      - Put output in ${CMAKE_CURRENT_BINARY_DIR}${CMAKE_FILES_DIRECTORY}
      - Remove try_compile variable from the cache after using
      8756e77f
    • Todd Gamblin's avatar
      Try regular compiler when no MPI compiler. · e00d2c4d
      Todd Gamblin authored
      If FindMPI can't interrogate any of the available compilers, it attempts to compile simple MPI
      programs with CMAKE_${lang}_COMPILER.  If this works, it uses that as MPI_${lang}_COMPILER.
      
      This allows MPI to be discovered on Cray XT/XE systems, where modules are used and cc, CC, and ftn
      compilers *are* MPI compilers.
      e00d2c4d
  21. 24 Apr, 2011 1 commit
  22. 16 Mar, 2011 1 commit
    • Brad King's avatar
      FindMPI: Fix documentation formatting · a32a6332
      Brad King authored
      Adjust whitespace to make the output of "--help-module FindMPI" look
      good.  Also separate the comment containing the copyright and license
      notice so it does not appear in the documentation.
      a32a6332
  23. 15 Mar, 2011 1 commit
    • Todd Gamblin's avatar
      FindMPI: Handle multiple languages · 706b73e8
      Todd Gamblin authored
      Adds support for:
      
      - MPI_<lang>_COMPILER and other useful variables for C, CXX, Fortran
      - Better compiler interrogation (handles mvapich)
      - Supports specifying an MPI compiler name directly on the command line
        without and absolute path, e.g.: cmake -D MPI_CXX_COMPILER=mpixlC
      - Better compiler name searching tries to match MPI compiler to regular
        CMAKE_<lang>_COMPILER_ID, if it's available.
      
      Gets rid of:
      
      - MPI_LIBRARY, MPI_EXTRA_LIBRARY cache variables.  These and other old
        vars are still exported for backward compatibility, but they're not
        cached.
      706b73e8
  24. 20 Jan, 2011 1 commit
    • Brad King's avatar
      Modules: Include builtin FindPackageHandleStandardArgs directly · c4275592
      Brad King authored
      The FindPackageHandleStandardArgs module was originally created outside
      of CMake.  It was added for CMake 2.6.0 by commit e118a627 (add a macro
      FIND_PACKAGE_HANDLE_STANDARD_ARGS..., 2007-07-18).  However, it also
      proliferated into a number of other projects that at the time required
      only CMake 2.4 and thus could not depend on CMake to provide the module.
      CMake's own find modules started using the module in commit b5f656e0
      (use the new FIND_PACKAGE_HANDLE_STANDARD_ARGS in some of the FindXXX
      modules..., 2007-07-18).
      
      Then commit d358cf5c (add 2nd, more powerful mode to
      find_package_handle_standard_args, 2010-07-29) added a new feature to
      the interface of the module that was fully optional and backward
      compatible with all existing users of the module.  Later commit 5f183caa
      (FindZLIB: use the FPHSA version mode, 2010-08-04) and others shortly
      thereafter started using the new interface in CMake's own find modules.
      This change was also backward compatible because it was only an
      implementation detail within each module.
      
      Unforutnately these changes introduced a problem for projects that still
      have an old copy of FindPackageHandleStandardArgs in CMAKE_MODULE_PATH.
      When any such project uses one of CMake's builtin find modules the line
      
        include(FindPackageHandleStandardArgs)
      
      loads the copy from the project which does not have the new interface!
      Then the including find module tries to use the new interface with the
      old module and fails.
      
      Whether this breakage can be considered a backward incompatible change
      in CMake is debatable.  The situation is analagous to copying a standard
      library header from one version of a compiler into a project and then
      observing problems when the next version of the compiler reports errors
      in its other headers that depend on its new version of the original
      header.  Nevertheless it is a change to CMake that causes problems for
      projects that worked with previous versions.
      
      This problem was discovered during the 2.8.3 release candidate cycle.
      It is an instance of a more general problem with projects that provide
      their own versions of CMake modules when other CMake modules depend on
      them.  At the time we resolved this instance of the problem with commit
      b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake
      everywhere, 2010-09-28) for the 2.8.3 release.
      
      In order to address the more general problem we introduced policy
      CMP0017 in commit db44848f (Prefer files from CMAKE_ROOT when including
      from CMAKE_ROOT, 2010-11-17).  That change was followed by commit
      ce28737c (Remove usage of CMAKE_CURRENT_LIST_DIR now that we have
      CMP0017, 2010-12-20) which reverted the original workaround in favor of
      using the policy.  However, existing project releases do not set the
      policy behavior to NEW and therefore still exhibit the problem.
      
      We introduced in commit a364daf1 (Allow users to specify defaults for
      unset policies, 2011-01-03) an option for users to build existing
      projects by adding -DCMAKE_POLICY_DEFAULT_CMP0017=NEW to the command
      line.  Unfortunately this solution still does not allow such projects to
      build out of the box, and there is no good way to suggest the use of the
      new option.
      
      The only remaining solution to keep existing projects that exhibit this
      problem building is to restore the change originally made in commit
      b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake
      everywhere, 2010-09-28).  This also avoids policy CMP0017 warnings for
      this particular instance of the problem the policy addresses.
      c4275592
  25. 04 Jan, 2011 1 commit
  26. 11 Oct, 2010 1 commit
  27. 28 Sep, 2010 1 commit
  28. 20 Sep, 2010 1 commit
    • Brad King's avatar
      FindMPI: Recoginze -f flags from mpicc (#10771) · a56969f3
      Brad King authored
      Parse compiler flags like "-fmessage-length=0 -fstack-protector
      -funwind-tables -fasynchronous-unwind-tables -fno-strict-aliasing" from
      the output of "mpicc -show".  We already handle preprocessor definition
      arguments like -DUSE_STDARG.  Honor '-f' flags too.
      a56969f3
  29. 09 Aug, 2010 1 commit
  30. 29 Jun, 2010 1 commit
  31. 28 Jun, 2010 2 commits
  32. 25 Jun, 2010 1 commit
  33. 24 Jun, 2010 1 commit
  34. 16 Mar, 2010 1 commit
  35. 11 Mar, 2010 1 commit