)]}'
{
  "commit": "4061692ba427af2085e934e0734926f93ea2c823",
  "tree": "73e520bac59fec49bd9d0570d84f1dd87e9ad0e1",
  "parents": [
    "574ac610761495b7b7afcced7717188501402925"
  ],
  "author": {
    "name": "Toon Claes",
    "email": "toon@iotcl.com",
    "time": "Wed Dec 03 15:53:31 2025 +0100"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Dec 05 11:11:15 2025 +0900"
  },
  "message": "meson: use is_cross_build() where possible\n\nIn previous commit the first use of meson.can_run_host_binaries() was\nintroduced. This is a guard around compiler.run() to ensure it\u0027s\nactually possible to execute the provided.\n\nIn other places we\u0027ve been having the same issue, but here `not\nmeson.is_cross_build()` is used as guard. This does the trick, but it\nalso prevents the code from running even when an exe_wrapper is\nconfigured.\n\nSwitch to using meson.can_run_host_binaries() here as well.\n\nThere is another place left that still uses `not\nmeson.is_cross_build()`, but here it\u0027s a guard around fs.exists(). That\nfunction will always run on the build machine, so checking for\ncross-compilation is still in place here.\n\nSigned-off-by: Toon Claes \u003ctoon@iotcl.com\u003e\nAcked-by: Patrick Steinhardt \u003cps@pks.im\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "95348e69a413a928cb5017e111b8e3f110420245",
      "old_mode": 33188,
      "old_path": "meson.build",
      "new_id": "00ad8a5c6011e559aa71e2d408f1ee2e6751d1e6",
      "new_mode": 33188,
      "new_path": "meson.build"
    }
  ]
}