1. 29 Jun, 2017 1 commit
    • Robert Dailey's avatar
      FindDoxygen: Use a stable reference to the location of global resources · 97a9a356
      Robert Dailey authored
      FindDoxygen generates some files based on the version of Doxygen whose
      content will not vary across a project and are therefore a global
      resource that can be shared by all calls to `find_package(Doxygen)` and
      to `doxygen_add_docs`.  We currently use `${PROJECT_BINARY_DIR}` to
      reference their location, but this is not stable because `project()`
      calls in a subdirectory can change it.  Use `${CMAKE_BINARY_DIR}`
      Reviewed-by: Craig Scott's avatarCraig Scott <craig.scott@crascit.com>
      Fixes: #17022
  2. 28 Jun, 2017 7 commits
    • Brad King's avatar
    • Ian Hojnicki's avatar
      VS: Add v140 and v141 flag table entries for /DEBUG:NONE and /DEBUG:FULL · 7ba27e36
      Ian Hojnicki authored and Brad King's avatar Brad King committed
    • Brad King's avatar
      VS: Fix GenerateDebugInformation values for v140 and v141 toolsets · ae44496e
      Brad King authored
      When VS 2015 was first released, its new v140 toolset came with a
      `link.xml` file that changed the `GenerateDebugInformation` boolean
      (`false` and `true`) value from earlier toolsets to an enumeration
      consisting of the possible values `No`, `Debug`, and `DebugFastLink`.
      We first adapted to this in commit v3.4.2~2^2 (VS: Fix VS 2015 .vcxproj
      file value for GenerateDebugInformation, 2016-01-08), but that broke
      older toolsets that still expected the boolean.  Then commit
      v3.6.0-rc1~295^2~1 (VS: Fix VS 2015 .vcxproj debug setting for older
      toolsets, 2016-02-24) added a hack to fix up the value based on the
      toolset in use.  Several follow-up commits fixed this for more older
      toolsets because our flag table was at the time based on the generator
      in use rather than the toolset in use.
      Since commit v3.8.0-rc1~396^2 (VS: Choose flag map based on the toolset
      name, 2016-10-17) we use a flag table based on the toolset, so the fixup
      hack should not be needed.  We had to keep it around only due to our
      default value for GenerateDebugInformation (`false` or `No`) still being
      based on the generator instead of the toolset.
      A VS 2015 update was released that changed the v140 toolset `link.xml`
      file back to using `false` and `true` for the `GenerateDebugInformation`
      enumeration variants previously known as `No` and `Debug`.  In order to
      know which pair to use, we need to parse the `link.xml` file for the
      current toolset.
      Switch back to using `false` and `true` unconditionally in our
      `GenerateDebugInformation` flag table entries and default value.  With
      that plus the toolset-based flag table, we now get incorrect values for
      `GenerateDebugInformation` only when using a v140 toolset from an older
      VS 2015 installation.  Detect this case by parsing `link.xml` and add
      special logic to convert `false` and `true` to `No` and `Debug` to
      satisfy the older toolset specification.
      Inspired-by: default avatarIan Hojnicki <nullref@live.com>
      Fixes: #17020
    • Ian Hojnicki's avatar
      VS: Fix GenerateDebugInformation flag map text for v141 toolsets · 27bef160
      Ian Hojnicki authored and Brad King's avatar Brad King committed
      Update the help text to match that from v141's link.xml file.
    • Ian Hojnicki's avatar
      VS: Split link flag table between v140 and v141 toolsets · 17a397c2
      Ian Hojnicki authored and Brad King's avatar Brad King committed
    • Brad King's avatar
      Merge branch 'curl-haiku' into release-3.9 · 9807a0ce
      Brad King authored
    • Jérôme Duval's avatar
      curl: Fix build on Haiku · e7936751
      Jérôme Duval authored and Brad King's avatar Brad King committed
      On Haiku the network functions are in libnetwork, so use it when it
  3. 27 Jun, 2017 6 commits
  4. 26 Jun, 2017 4 commits
  5. 22 Jun, 2017 7 commits
  6. 21 Jun, 2017 5 commits
  7. 20 Jun, 2017 4 commits
  8. 19 Jun, 2017 3 commits
  9. 15 Jun, 2017 3 commits