1. 30 Apr, 2014 2 commits
    • Brad King's avatar
    • Brad King's avatar
      ExternalProject: Fix path to cmake in verify script · 420280f3
      Brad King authored
      In commit v3.0.0-rc1~103^2~3 (ExternalProject: Reattempt download when
      verification fails, 2014-01-15) a reference to ${CMAKE_COMMAND} was
      added to generate a reference to the CMake command in a cmake script.
      Escape the '$' so that the literal variable reference appears in the
      script instead of writing the path to the current cmake.  This is
      necessary when the path to CMake contains spaces or other characters
      special to CMake syntax.
  2. 25 Apr, 2014 3 commits
  3. 24 Apr, 2014 3 commits
  4. 22 Apr, 2014 2 commits
  5. 18 Apr, 2014 2 commits
  6. 16 Apr, 2014 5 commits
  7. 11 Apr, 2014 3 commits
  8. 10 Apr, 2014 6 commits
  9. 03 Apr, 2014 2 commits
    • Brad King's avatar
    • Robert Maynard's avatar
      Qt4Macros: Make QT4_CREATE_MOC_COMMAND a function · 7beba986
      Robert Maynard authored and Brad King's avatar Brad King committed
      QT4_CREATE_MOC_COMMAND is given a moc_flags argument that contains the
      COMPILE_DEFINITIONS and a potentially large list of include directories.
      Since it is a macro, the ${moc_flags} reference is replaced with this
      content and sent through cmMakefile::ExpandVariablesInString (EVIS).
      Since commit v3.0.0-rc1~138^2 (Qt4: Use generator expression in
      COMPILE_DEFINITIONS, 2014-01-13) the COMPILE_DEFINITIONS value contains
      a '$' so the EVIS fast-path is no longer used.  Instead the full
      cmCommandArgumentParserHelper is now used on the large input, which is
      very slow (since it was originally created for hand-written code).
      Change QT4_CREATE_MOC_COMMAND to a function instead of a macro to avoid
      passing large content through EVIS.  This makes it significantly faster.
  10. 02 Apr, 2014 5 commits
    • Brad King's avatar
    • Brad King's avatar
      Do not warn by default when policy CMP0025 or CMP0047 is not set · a41c0a9d
      Brad King authored
      These policies are triggered by the use of a particular compiler rather
      than outdated CMake code in a project.  Avoid warning in every project
      that enables a language by not displaying the policy warning by default.
      Add variable CMAKE_POLICY_WARNING_CMP<NNNN> to control the warning
      explicitly; otherwise enable the warning with --debug-output or --trace.
      This breaks with strict policy convention because it does not provide
      developers with any warning about the behavior change by default.
      Existing projects will continue to build without a warning or change in
      behavior.  When a developer changes the minimum required version of
      CMake in a project to a sufficiently high value (3.0), the project will
      suddenly get the new compiler id and may break, but at least the
      breakage comes with a change to the project rather than the version of
      CMake used to build it.
      Breaking strict policy convention is worthwhile in this case because
      very few projects will be affected by the behavior change but every
      project would have to see the warning if it were enabled by default.
    • Brad King's avatar
      Help: Revise and format policy CMP0025 and CMP0047 docs · d339653e
      Brad King authored
      Add inline reST markup as appropriate.  Word CMP0047 docs more like
      those of CMP0025.  State explicitly that the policies must be set
      before the project or enable_language command calls.
    • Brad King's avatar
    • Brad King's avatar
      Merge branch 'clang-warnings' into release · b783b99f
      Brad King authored
  11. 31 Mar, 2014 2 commits
  12. 26 Mar, 2014 2 commits
  13. 20 Mar, 2014 1 commit
  14. 19 Mar, 2014 2 commits