1. 24 Aug, 2017 1 commit
    • Brad King's avatar
      Xcode: Revert addition of "outputPaths" to custom command build phase · 9ecee256
      Brad King authored
      The change in commit v3.9.0~3^2 (Xcode: Add "outputPaths" to custom
      command script build phase, 2017-07-13) was meant to support Xcode 9's
      new build system.  However, without matching "inputPaths", Xcode will
      not re-run the build phase if its outputs have already been generated.
      This broke the old Xcode build system too.
      Revert the change for now so at least the old Xcode build system works.
      Further investigation will be needed to add proper support for Xcode 9's
      new build system.
      Fixes: #17178
  2. 22 Aug, 2017 1 commit
    • Brad King's avatar
      macOS: Revert default Hi-DPI support in applications · 286c75f7
      Brad King authored
      This reverts commit v3.9.0-rc1~287^2 (macOS: Enable Hi-DPI support in
      applications by default, 2017-04-08).  It breaks iOS applications that
      do not use their own `MACOSX_BUNDLE_INFO_PLIST` because `NSApplication`
      is only for macOS apps.  Until more complete support for iOS is added
      to CMake (e.g. with a different default plist file) we must allow
      our default plist file to work for both macOS and iOS.
      Fixes: #17179
  3. 08 Aug, 2017 1 commit
    • Brad King's avatar
      find_*: Disable the PACKAGE_ROOT search path group for CMake 3.9 · 578d95f8
      Brad King authored
      Disable the feature added by commit v3.9.0-rc1~71^2~2 (find_*: Add a new
      PackageRoot search path group, 2017-05-03) and remove documentation
      added by commit v3.9.0-rc1~71^2 (find_*: Add docs for PackageRoot search
      path group, 2017-05-03).  Unfortunately the name `<pkg>_ROOT` may
      already be set by projects for their own incompatible purposes.  Disable
      the behavior change for now to fix the regression for CMake 3.9.  We can
      restore it later with a policy.
      In order to keep the implementation and tests working, add an
      undocumented variable we can use in the tests to enable the behavior
      before the policy is introduced.
      Fixes: #17144
  4. 03 Aug, 2017 1 commit
  5. 14 Jul, 2017 2 commits
  6. 20 Jun, 2017 1 commit
  7. 15 Jun, 2017 1 commit
  8. 14 Jun, 2017 1 commit
  9. 12 Jun, 2017 1 commit
  10. 07 Jun, 2017 1 commit
  11. 05 Jun, 2017 1 commit
  12. 02 Jun, 2017 2 commits
    • Brad King's avatar
      Help: Organize and revise 3.9 release notes · 945cb9aa
      Brad King authored
      Add section headers similar to the 3.8 release notes and move each
      individual bullet into an appropriate section.  Revise a few bullets.
    • Brad King's avatar
      Help: Consolidate 3.9 release notes · 7bc26430
      Brad King authored
      Move all development release notes into a new version-specific document:
          tail -q -n +3 Help/release/dev/* > Help/release/3.9.rst
          git rm -- Help/release/dev/*
      except the sample topic:
          git checkout HEAD -- Help/release/dev/0-sample-topic.rst
      Reference the new document from the release notes index document.
      Add a title and intro sentence to the new document by hand.
  13. 26 May, 2017 2 commits
  14. 23 May, 2017 1 commit
    • Alex Turbov's avatar
      Improve Doxygen support · 59ffabfe
      Alex Turbov authored
      Except Graphviz's `dot` Doxygen may use few other utilities like
      `mscgen` (Message Sequence Chart) and `dia` (Diagram Editor).
      Now this module allows to manage Doxygen settings from `CMakeLists.txt`
      and forget about `Doxyfile`s. Also it provides a helper function
      to add a target to generate documentation: `doxygen_add_docs`.
      Implement code review notes:
      - Introduce `COMPONENTS` to find: `dot`, `mscgen` and `dia`;
      - Deprecate variables `DOXYGEN_SKIP_DOT`, `DOXYGEN_EXECUTABLE`,
        `doxygen_add_docs ` usage instead;
      - Properly handle paths to found tools in Windows;
      - Prevent adding a custom target if Doxygen was not really found;
      - Introduce exported (executable) targets for found components.
      Co-Author: Craig Scott <craig.scott@crascit.com>
  15. 19 May, 2017 1 commit
  16. 18 May, 2017 1 commit
  17. 16 May, 2017 1 commit
  18. 15 May, 2017 1 commit
    • Craig Scott's avatar
      GoogleTest: Expand capabilities of gtest_add_tests() · 6edd1806
      Craig Scott authored
      Now has keyword-based arguments (old syntax form is still supported).
      Discovered tests can have a prefix and/or suffix added to the test names
      and the list of discovered tests is available to the caller. The working
      dir can also be set and the dependency on the source files is now
      optional instead of mandatory.
  19. 12 May, 2017 1 commit
    • Konstantin Podsvirov's avatar
      CPackIFW: Internationalization Support · 72ac7ad9
      Konstantin Podsvirov authored
      - DISPLAY_NAME and DESCRIPTION in CPackIFW module now is MULTI_ARGS;
      - Added internationalization support for DisplayName and Description
        properties in cmCPackIFWPackage class;
      - Added documentation to CPackIFW module;
      - Added release note.
  20. 09 May, 2017 1 commit
    • Brad King's avatar
      Add options for separate compile and link sysroots · 53e89b6a
      Brad King authored
      Add `CMAKE_SYSROOT_COMPILE` and `CMAKE_SYSROOT_LINK` variables to as
      operation-specific alternatives to `CMAKE_SYSROOT`.  This will be useful
      for Android NDKs that compile and link with different sysroot values
      (e.g. `r14` with unified headers).
      Co-Author: Florent Castelli <florent.castelli@gmail.com>
  21. 04 May, 2017 1 commit
    • Zack Galbreath's avatar
      ctest_submit: Add HTTPHEADER option · 1a7d00bd
      Zack Galbreath authored
      Allow CTest script writers to specify additional HTTP headers to be sent
      to CDash during submission.
      The motivating case for this feature is a corresponding change in CDash.
      This will allow projects to refuse submissions from any site not bearing
      a valid authentication token.
  22. 01 May, 2017 1 commit
  23. 26 Apr, 2017 1 commit
  24. 24 Apr, 2017 2 commits
  25. 22 Apr, 2017 1 commit
  26. 21 Apr, 2017 3 commits
  27. 20 Apr, 2017 1 commit
  28. 19 Apr, 2017 1 commit
  29. 18 Apr, 2017 3 commits
  30. 15 Apr, 2017 1 commit
  31. 14 Apr, 2017 1 commit
  32. 11 Apr, 2017 1 commit
    • Alex Turbov's avatar
      project: Add `DESCRIPTION` parameter · 3b484871
      Alex Turbov authored
      It is quite often the project description has used in a real world software.
      Examples include:
      * part of a help screen of the application
      * builtin resources (`*.rc` files, data for "About" dialog of a GUI app, & etc)
      * most generators for CPack can use it
      * it could be used by documentary software (Doxygen, Sphinx) which is usually
        integrated to CMake based projects via `add_custom_target()`
      Now `project()` call learned an optional `DESCRIPTION` parameter with a
      short string describing a project. Being specified, it would set the
      `PROJECT_DESCRIPTION` variable which could be used in `configure_file()`
      or whatever user wants.  Also `PROJECT_DESCRIPTION` is a default value