)]}'
{
  "commit": "80f2a1f56f364e58b9cf6e1d110587a42e8993eb",
  "tree": "ebbff68be88ceefafa0921a6153a483c3c0d4123",
  "parents": [
    "e93f701f2a9c2be577d0e0f0b7c6ce2d84aa11d8",
    "ebfd0b8fc14fcba22e4e1fadb12ffec5d42642e5"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Fri Feb 14 14:18:19 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Feb 14 14:18:19 2020 +0000"
  },
  "message": "Merge #137\n\n137: Enable support for multiple boards and architectures r\u003dWoyten a\u003dWoyten\n\nThis PR is a starting point to support multiple boards and architectures. The design is as follows:\r\n\r\n- Before the code is compiled a `build.rs` script selects an appropriate linker script. This selection is based on whether the environment variable `PLATFORM` is set or the file `platform` is present.\r\n- When using `cargo run` on an embedded target architecture, the script `flash.sh` is executed instead of directly running the binary. `flash.sh` is a replacement for `run_example` and contains a new but incomplete dispatching section which determines the appropriate `tockloader_flags` for the currently selected platform.\r\n- Aliases like `cargo rtv7em` are shorthand for `run --release --target\u003dthumbv7em-none-eabi --example`\n\nCo-authored-by: Woyten \u003cwoyten.tielesch@online.de\u003e\n",
  "tree_diff": []
}