1. 14 Feb, 2019 3 commits
  2. 06 Feb, 2019 1 commit
  3. 05 Feb, 2019 3 commits
  4. 04 Feb, 2019 3 commits
  5. 03 Feb, 2019 1 commit
  6. 02 Feb, 2019 5 commits
  7. 01 Feb, 2019 8 commits
  8. 31 Jan, 2019 4 commits
  9. 30 Jan, 2019 12 commits
    • Harry Mallon's avatar
      install: Fix stripping on macOS · 20291e8e
      Harry Mallon authored
      On macOS the `strip` tool requires special arguments depending on the
      type of binary to be stripped.
      
      Fixes: #11367
      Fixes: #16499
      20291e8e
    • Brad King's avatar
      Ninja: Use deps=gcc for Intel Compiler on Windows · a624a3e1
      Brad King authored
      Ninja 1.9 supports the depfile format generated by this compiler.
      Use `deps = gcc` when the version of Ninja is new enough.
      
      Unfortunately the Intel Compiler for Windows does not properly
      escape spaces in paths written to a depfile so if there is a
      space in the path we must still fall back to `deps = msvc`.
      
      Fixes: #18855
      a624a3e1
    • Brad King's avatar
      Ninja: Detect when ninja is new enough to support a multi-line depfile · f4f3b6b9
      Brad King authored
      Ninja 1.9 supports the multi-line depfile format generated by the
      Intel Compiler for Windows.  Teach the global generator to detect
      when the version is new enough to support this.
      f4f3b6b9
    • Brad King's avatar
      Ninja: Drop unnecessary deptype customization infrastructure · 699cd032
      Brad King authored
      Do not pass `CMAKE_NINJA_DEPTYPE_<LANG>` in place of `deps = gcc`.
      If Ninja ever introduces a new dependency type we will likely need
      to update CMake for it anyway.
      699cd032
    • wahikihiki's avatar
      OutputCallback: Accept std::string argument · 1180fc87
      wahikihiki authored
      1180fc87
    • wahikihiki's avatar
      clang-tidy: Silence use-equals-default warning · 3f9822ff
      wahikihiki authored
      clang-tidy 7 has an option to suppress this warning in macros which
      defaults to '1'.  Set the option to '0' and silence the warning
      explicitly.
      3f9822ff
    • Sebastian Holtermann's avatar
      Autogen: Read the Qt version from directory properties as well · 062d21c3
      Sebastian Holtermann authored
      This lets AUTOGEN read the Qt version from directory properties as a fallback
      when the Qt version variables are empty or unset.
      062d21c3
    • Taylor holberton's avatar
      198650ae
    • Ben Boeckel's avatar
      AutoGen: query Qt5 version from directory properties · 2df6d690
      Ben Boeckel authored
      This allows functions which enable AutoGen to make the version variables
      available at generate time.
      
      See: #18732
      2df6d690
    • Brad King's avatar
      Xcode: Fix object library builds with sanitizers enabled · 8a7f93d0
      Brad King authored
      Using `xcodebuild -enableAddressSanitizer YES ...` causes object files
      to be placed in a different directory name.  Xcode provides a
      placeholder for this that we can use in `OTHER_LDFLAGS` to reference
      object files for linking the dependents of object libraries.  However,
      CMake's features for installing and exporting object libraries depend on
      knowing the real path with no placeholders.  For these cases, use the
      default object directory.  Users will then have to choose between
      sanitizers and the installation and export features, but both will work
      individually.
      
      Fixes: #16289
      8a7f93d0
    • Brad King's avatar
      Xcode: Place object library artifacts outside Objects-normal directory · eff9c697
      Brad King authored
      The `CONFIGURATION_BUILD_DIR` value in the Xcode project file specifies
      where to place the library artifact.  For object libraries we've used
      the `Objects-normal` directory to hide away the `.a` that we otherwise
      cannot stop Xcode from producing.  The parent of this directory is also
      specific to the target and does not vary with Xcode's sanitizer
      features, so move the artifact there.
      
      Issue: #16289
      eff9c697
    • Brad King's avatar
      macOS: Restore compatibility for setting FRAMEWORK after install() · 95210d02
      Brad King authored
      The `FRAMEWORK` target property affects the way the `install()` command
      treats the target and so should be set first.  Our implementation
      assumed that this was always the case and led to an assertion failure.
      Prior to CMake 3.12 this was visible only when using an explicit
      `LIBRARY ... NAMELINK_ONLY` option, but commit 0212d7c7 (install: add
      NAMELINK_COMPONENT argument, 2018-04-18, v3.12.0-rc1~139^2~3) made
      it possible with a simple `LIBRARY DESTINATION`.
      
      Fully supporting out-of-order specification will require non-trivial
      refactoring to defer install generator creation to generate time.
      For now simply restore the old behavior of installing the framework
      to the library destination and warn about the case.
      
      Fixes: #18848
      95210d02