Skip to content
Snippets Groups Projects
  1. Feb 05, 2016
  2. Dec 28, 2015
  3. Dec 03, 2015
  4. Sep 24, 2015
  5. Sep 12, 2015
  6. Sep 01, 2015
  7. Aug 25, 2015
    • Carsten Gräser's avatar
    • Markus Blatt's avatar
      [release] Always indicate whether we support parallelism. · 9985ff38
      Markus Blatt authored
      
      Since commit 495f2fce USE_MPI was removed from dunecontrol and
      the default configuration now defaults to use
      parallelism. Unfortunately, there are downstream modules that try to
      support multiple versions of DUNE. Sometimes these need to decide
      whether to support parallelism before they know which version of DUNE
      they are using. This is was not possible when providing
      --enable-parallel as no variable gets set for DUNE>=2.4.
      
      With this commit dunecontrol always sets
      CMAKE_DISABLE_FIND_PACKAGE_MPI to an appropriate value. Thus if
      dunecontrol is used then one can check in one's own module whether the
      variable is set explicitly to false and conclude that one is using
      >=2.4 and wants parallelism. Otherwise one can check USE_MPI to detect
      which behaviour is needed for 2.3.
      
      E.g. like this:
      <code>
      option (USE_MPI "Use Message Passing Interface for parallel computing" OFF)
      
      if( NOT CMAKE_DISABLE_FIND_PACKAGE_MPI STREQUAL ""
          AND NOT CMAKE_DISABLE_FIND_PACKAGE_MPI)
        set(USE_MPI ON)
      endif()
      
      if (NOT USE_MPI)
            set (CMAKE_DISABLE_FIND_PACKAGE_MPI TRUE)
       set (CMAKE_DISABLE_FIND_PACKAGE_MPI TRUE)
      endif (NOT USE_MPI)
      </code>
      
      Of course without dunecontrol and using the defaults one will still
      configure DUNE as parallel, but one's own module as sequential.
      
      (cherry picked from commit 14371eb3)
      Signed-off-by: default avatarCarsten Gräser <graeser@dune-project.org>
      9985ff38
    • Markus Blatt's avatar
      [release] Make finding *.la files non-fatal. · 8f482bf8
      Markus Blatt authored
      
      Actually, having these files lying around does not hurt us.
      In addition there are downstream modules that especially create
      these for compatibility reasons with autotools. For these
      reconfiguring a module using dunecontrol currently aborts with an error
      
      Therefore this commit resorts to just issuing a warning and proceeding
      with the compilation instead of aborting with an error.
      
      (cherry picked from commit 21dbaefe)
      Signed-off-by: default avatarCarsten Gräser <graeser@dune-project.org>
      8f482bf8
  8. Aug 24, 2015
  9. Aug 19, 2015
  10. Aug 18, 2015
  11. Jul 17, 2015
  12. Jul 10, 2015
Loading