1. 30 Nov, 2016 2 commits
  2. 29 Nov, 2016 1 commit
  3. 28 Nov, 2016 1 commit
  4. 14 Nov, 2016 2 commits
  5. 11 Nov, 2016 1 commit
  6. 09 Nov, 2016 1 commit
    • Brad King's avatar
      QtAutogen: Do not re-generate AUTORCC outputs on every build · e4232b82
      Brad King authored
      Refactoring in commit v3.6.0-rc1~134^2~10 (Autogen: Split out moc file
      generation code to dedicated method, 2016-04-18) removed the
      unconditional creation of the `<target>_automoc.cpp` file.  Now it is
      generated only when `AUTOMOC` is enabled.  However, if this file is not
      created then our internal `GenerateAll` setting is enabled on every
      build, causing `AUTORCC` to re-generate its file(s) every time.  Fix the
      `GenerateAll` setting to be used only for when autogen settings change.
      The old logic was left from when we had only automoc.
      Closes: #16413
  7. 04 Nov, 2016 1 commit
  8. 28 Oct, 2016 1 commit
  9. 27 Oct, 2016 1 commit
  10. 24 Oct, 2016 2 commits
    • Brad King's avatar
      cmake-server: Change message wrapper to avoid ambiguity with content · 9b8dc79c
      Brad King authored
      Change our message wrapper from
          [== CMake Server ==[ ... ]== CMake Server ==]
          [== "CMake Server" ==[ ... ]== "CMake Server" ==]
      to guarantee that no JSON content can ever contain the ending string
      (because it would be encoded as `]== \"CMake Server\" ==]`).
    • Alexis Murzeau's avatar
      Ninja: Use binary dir for `$subdir/all` targets · 42db2ebc
      Alexis Murzeau authored
      The targets added by commit v3.6.0-rc1~240^2~2 (Ninja: Add `$subdir/all`
      targets, 2016-03-11) use as `$subdir` the relative path from the top of
      the source tree to the current source directory.  This is not correct
      when using `add_subdirectory(test test_bin)`.  Instead we need to use
      the relative path from the top of the binary tree to the current binary
      directory as was done for related targets by commit v3.7.0-rc1~268^2
      (Ninja: Add `$subdir/{test,install,package}` targets, 2016-08-05).
  11. 19 Oct, 2016 1 commit
  12. 18 Oct, 2016 1 commit
    • Tobias Hunger's avatar
      server-mode: Fix named pipe mode · 9112c43e
      Tobias Hunger authored
      Do not treat a pointer itself as a `uv_stream_t`, but instead the
      pointed-to `uv_pipe_t`.  It is unclear how this ever worked before in
      local testing.
      While at it, remove duplicate setup code and improve an error message.
  13. 13 Oct, 2016 3 commits
    • Brad King's avatar
      Ninja: Fix POST_BUILD commands on macOS Frameworks · 20278872
      Brad King authored
      The condition added by commit v2.8.12~179^2 (OS X: Fix regression
      handling frameworks for Ninja, 2013-07-16) for excluding use of
      versioning symlinks on macOS Frameworks must match that used for
      POST_BUILD selection.  Otherwise we place the POST_BUILD commands after
      a symlink step that is never added.
      Closes: #16363
    • Jamie Snape's avatar
      Honor LINK_WHAT_YOU_USE when set to OFF · 933e54d3
      Jamie Snape authored
      Explicitly setting variable CMAKE_LINK_WHAT_YOU_USE or property
      LINK_WHAT_YOU_USE to OFF should not cause LWYU to run.  Fix the
      property lookup to use GetPropertyAsBool.
    • Ben Boeckel's avatar
      Ninja: Fix RC language depfile generation with cmcldeps · 9977899d
      Ben Boeckel authored
      In commit v3.7.0-rc1~275^2 (Ninja: Use full path for all source files,
      2016-08-05), the source path was changed to use an absolute path.
      Inside of `cmcldeps` for `.rc` file compilation, it uses a separate
      argument for the path to the source file.  This ended up causing
      `cmcldeps` to transform the following call:
          cmcldeps.exe RC source.rc ... C:/full/path/to/source.rc
          ... C:/full/path/to//Tc source.rc
      which is invalid.  Update the source filename to use the full path to
      the source file so that the path is replaced properly.
  14. 11 Oct, 2016 1 commit
    • Brad King's avatar
      cmake-gui: Fix "extra" generator entries in drop-down list · bf86012a
      Brad King authored
      Refactoring in commit v3.7.0-rc1~291^2~1 (Refactor extra generator
      registration to use factories, 2016-07-20) accidentally switched
      the order of the "extra - base" generator names to "base - extra".
      Switch it back.  While this could affect all callers of the
      `GetRegisteredGenerators` method, only cmake-gui actually used this
      particular field.
      Closes: #16359
  15. 10 Oct, 2016 1 commit
    • Brad King's avatar
      VS: Split flag table between v140 and v141 toolsets · b1d67ae8
      Brad King authored
      In commit v3.7.0-rc1~156^2~1 (VS: Update v140 flag tables from VS 15
      MSBuild files, 2016-09-02) we extended the v140 flag table with values
      from the v141 toolset that comes with VS 15.  However, the v140 toolset
      that comes with VS 14 does not have all of these entries and so the
      flags just need to be passed without special mapping.  In order to
      support both toolsets, split our CL flag table into separate copies for
      each version and switch off the toolset name.
      Closes: #16352
  16. 07 Oct, 2016 2 commits
  17. 06 Oct, 2016 2 commits
    • Brad King's avatar
      VS: Update VS 15 generator for Preview 5 · 02b7d278
      Brad King authored
      The `PlatformToolset` is now `v141` instead of `v140`.
      Closes: #16347
    • Stephen Kelly's avatar
      cmGlobalGenerator: Add API to get settings from top-level cmMakefile · f59e8779
      Stephen Kelly authored
      At generate-time, definitions are sometimes read from a nearby cmMakefile,
      making the value directory-specific because they are read once per
      directory.  Often however, the intention is more
      often to create a 'global' setting, such that the user writes for
       set(CMAKE_IMPORT_LIBRARY_SUFFIX something)
      once at the top level of their project.
      Many of these are also set by internal platform files, such as
      The set() definitions are not really suitable for 'global' settings
      because they can be different for each directory, and code consuming the
      settings must assume they are different for each directory, and read it
      freshly each time with new allocations.
      CMake has other variable types which are global in scope, such as global
      properties, and cache variables.  These are less convenient to populate
      for users, so establish a convention and API using the value as it is at
      the end of the top-level CMakeLists file.
  18. 05 Oct, 2016 1 commit
  19. 04 Oct, 2016 2 commits
  20. 03 Oct, 2016 2 commits
  21. 02 Oct, 2016 1 commit
  22. 01 Oct, 2016 1 commit
  23. 30 Sep, 2016 5 commits
  24. 29 Sep, 2016 4 commits