)]}'
{
  "commit": "80c29efc1c8a823dd8de94693ea2955377d6146f",
  "tree": "32cfa72dcad8eb452d201515c2d856aa7702ccd9",
  "parents": [
    "b70d8f12f401852fc683ddad38fdd701484725f8"
  ],
  "author": {
    "name": "Keith Smiley",
    "email": "keithbsmiley@gmail.com",
    "time": "Thu Jun 11 17:09:39 2026 -0700"
  },
  "committer": {
    "name": "Keith Smiley",
    "email": "keithbsmiley@gmail.com",
    "time": "Thu Jun 11 18:04:15 2026 -0700"
  },
  "message": "Make libtool wrapper handle ar args\n\nWhen interoping with other build systems, like through rules_rust or\nrules_foreign_cc, they often expect the `AR` env var to be set to the\nliteral `ar` command line tool. Apple currently ships an `ar` from the\n`cctools` repo that doesn\u0027t have the same hermeticity flags as `llvm-ar`\n(specifically it is lacking `D`). Because of this we use `libtool` which\nsupports `-D`. This change allows callers to not care about that\ndifference and pretend our wrapper is `ar`, and we still correctly\ncreate archives with libtool.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cf3165d153e7945991ec0df4290e2c4dd4ef9a10",
      "old_mode": 33188,
      "old_path": "crosstool/libtool.cc",
      "new_id": "f7b769580fdf87b92952c3e0ac79176377927b35",
      "new_mode": 33188,
      "new_path": "crosstool/libtool.cc"
    },
    {
      "type": "modify",
      "old_id": "4f67b0f19f083cc5bf29774e6b1d6f9fd2a468b4",
      "old_mode": 33188,
      "old_path": "test/shell/BUILD",
      "new_id": "a907b2132f40a526f773cf006b66a076e5a1220a",
      "new_mode": 33188,
      "new_path": "test/shell/BUILD"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "67157ed83e27c625b4c7c7b9afafad881566e1c9",
      "new_mode": 33261,
      "new_path": "test/shell/libtool_test.sh"
    }
  ]
}
