| commit | 515f87d88d0e10a221bc21f12bda365fbcf18176 | [log] [tgz] |
|---|---|---|
| author | tonglisayhi <tonglisayhi@google.com> | Thu Dec 13 17:24:42 2018 -0800 |
| committer | tonglisayhi <tonglisayhi@google.com> | Fri Dec 14 15:05:00 2018 -0800 |
| tree | 89c8b6cea1de6a65bae821b0b60add2ca6ffb34f | |
| parent | f758c7fd7d73e13de3334dc190488cc0f4fdabda [diff] |
[dump_breakpad_symbols] Have dump_breakpad_symbols produce an archive The go tool itself should do the tarring, as it easiest to do there where the tool has the relevant information; this would save the recipe from having to make brittle assumptions. If the build produced the archive directly, the recipe would have to do no more work beyond just uploading it, to the same downstream effect. IN-851 #comment Test: ninja -C out/x64 build/gn:breakpad_symbols #The desired tarball is generated Change-Id: I5ccd5911903fe5c2d577935eabbfc662ff87dec0
This repo contains tools used in Fuchsia build and development.
Go packages from here are automatically built and uploaded to CIPD and Google Storage by bots using the tools recipe. To add a tool to the build:
builder_mixins section with name: "tools".properties_j to add a string to the packages list:"fuchsia.googlesource.com/tools/cmd/your-new-tool"