Skip to content
Snippets Groups Projects
  1. Sep 01, 2015
  2. 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
  3. Aug 24, 2015
  4. Aug 19, 2015
  5. Aug 18, 2015
  6. Jul 17, 2015
  7. Jul 10, 2015
  8. Jul 07, 2015
  9. Jul 01, 2015
  10. Jun 30, 2015
    • Steffen Müthing's avatar
      [CMake][Release] Fix dune_enable_all_packages()-related problems · b3d8b8f8
      Steffen Müthing authored
      
      This branch fixes a number of problems related to
      dune_enable_all_packages():
      
      - The feature requires at least CMake 2.8.12, which is more recent than
        the baseline requirement of the core modules (2.8.12). We now check
        for that when executing the relevant functions and also remind the
        user to set the correct version in cmake_minimum_required().
      - Updated the documentation to also state the version requirement.
      - The duneproject script now also warns the user about the more
        stringent CMake version requirements when using the feature and sets
        the correct minimum required CMake version in the new module's main
        CMakeLists.txt file.
      - There was a bug in duneproject that caused it to always enable
        dune_enable_all_packages(), ignoring the choice made by the user. That
        bug is fixed in this branch.
      - Some minor fixes to duneproject while I was at it.
      
      This fixes FS1678.
      
      * feature/FS1678:
        [dunecontrol] Output choice of external package handling and required CMake version
        [duneproject] Allow specifying ENABLE_ALL as 5th command line argument
        [duneproject] Update CMake minimum version if ENABLE_ALL is true
        [duneproject][Bugfix] Make sure dune_enable_all_packages() can actually be disabled
        [CMake] Improve documentation in DuneEnableAllPackages.cmake
        [CMake][Doc] Add required CMake version to dune_enable_all_packages()
        [CMake] Require CMake 2.8.12 for dune_enable_all_packages()
        [CMake] Fix typo in warning message.
        Add a warning that some functions are 2.8.12
      
      (cherry picked from commit 90411efd)
      Signed-off-by: default avatarSteffen Müthing <muething@dune-project.org>
      b3d8b8f8
    • Oliver Sander's avatar
      Accept y,Y,n,N as an answer to a yes-no question · 2e05853b
      Oliver Sander authored
      
      Viz., the question on whether all packages should be enabled by default.
      
      This fixes FS 1647.
      
      (cherry picked from commit 20ac0ea1)
      Signed-off-by: default avatarSteffen Müthing <muething@dune-project.org>
      2e05853b
    • Oliver Sander's avatar
      Make the question on package enablement newbie-friendly · 93ea5100
      Oliver Sander authored
      
      (cherry picked from commit 58221538)
      Signed-off-by: default avatarSteffen Müthing <muething@dune-project.org>
      93ea5100
  11. Jun 25, 2015
Loading