)]}'
{
  "commit": "92859cc7484ac178e77825ccb86f95edcf0b6c49",
  "tree": "417e162d09321a927defa568fb5631c21aae18b3",
  "parents": [
    "8c4ec3b7b0d69649c04778a39eed5cdca338c1c0"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Mon Feb 27 12:37:19 2023 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Mon Feb 27 20:26:30 2023 +0000"
  },
  "message": "Fix the generated CMake build\n\nThis fixes two issues introduced in\n0e68520eb27b1f37038e9d0772cfee1d015b50c3. First, libssl never had a\ndependency on libcrypto, so the include directory did not get passed\nalong. Second, although this build (unlike the other CMake build)\ndoesn\u0027t define an install target, gRPC includes it and then pulls it\ninto its own install target. That then runs afoul of CMake\u0027s check\nagainst include directories in install targets.\n\nTo avoid this, condition the src/include directory on\n$\u003cBUILD_INTERFACE:...\u003e but omit a corresponding\n$\u003cINSTALL_INTERFACE:...\u003e. Since we\u0027re not the ones providing an install\ntarget, we don\u0027t actually know the value to use.\n\nPer [0], using the generator expression means we need to manually make\nit absolute ourselves.\n\n[0] https://cmake.org/cmake/help/latest/command/target_include_directories.html\n\nChange-Id: I2a25cc8382116c5957d94f65641220559b7af87d\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57685\nReviewed-by: Bob Beck \u003cbbe@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Bob Beck \u003cbbe@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "aec36bed82fa4560ca5d9d3fb714530b7ba4ec95",
      "old_mode": 33188,
      "old_path": "util/generate_build_files.py",
      "new_id": "386910b15b7be5cdfca83f095c3c41666ca8da09",
      "new_mode": 33188,
      "new_path": "util/generate_build_files.py"
    }
  ]
}