)]}'
{
  "commit": "f0570dbe98f19a958649f0d2e40467611c673ea9",
  "tree": "1f91f208a83953eaf632f636f9461795a93fef96",
  "parents": [
    "968fe6ba8984ec7ed1e515f90a701029ae67571a",
    "fdd0c3622d05a0bff9e0f4b7b1812df218dca291"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Tue Jan 19 22:48:30 2021 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Jan 19 22:48:30 2021 +0000"
  },
  "message": "Merge #268\n\n268: Add the libtock_runtime crate and platform switching. r\u003dhudson-ayers a\u003djrvanwhy\n\nThis is the first `libtock_runtime` PR. It contains:\r\n\r\nA. `Cargo.toml` for `libtock_runtime`\r\nB. Automatic linker script identification.\r\n\r\nThe automatic linker script identification is based on `libtock-rs`\u0027s current `build.rs` (in the root of the repository), but makes the following improvements:\r\n\r\nA. Better supports out-of-tree platforms by adding a cargo feature to disable linker script identification. `libtock-rs`\u0027s build.rs always emits a warning of the PLATFORM variable is not specified.\r\nB. Improves error handling, particularly around builds in paths we cannot support (e.g. if `cargo` is executed in a directory whose name contains a newline character).\r\nC. Moves the layout file location into `cargo`\u0027s `OUT_DIR`, which is the only directory build scripts are *supposed* to modify.\r\nD. Removes support for the `platform` file to select a platform. `libtock-rs` looked for a `platform` file in its own source to identify the platform it is run in -- I\u0027m not really sure how this was supposed to be used.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}