diff options
| author | Yi Sun <yi.sun@intel.corp-partner.google.com> | 2020-01-04 00:19:37 +0800 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-01-13 10:40:34 +0000 |
| commit | 54305cd5e2d52d274c20dd294c9c869a0115e96d (patch) | |
| tree | 8877329bb1f1b411068bf772876421dd04f777ad /disk | |
| parent | 4377f048e9258a06adfb8e990c2d616adda79d97 (diff) | |
| download | crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.tar crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.tar.gz crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.tar.bz2 crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.tar.lz crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.tar.xz crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.tar.zst crosvm-54305cd5e2d52d274c20dd294c9c869a0115e96d.zip | |
Add a new command to dump version info.
With command "version", we can dump version information via "crosvm version". By default it would dump the version specified in Cargo.toml like following: "crosvm package version 0.1.0". And if the environment varable "PKG_VERSION=123456" is given during building crosvm, it would dump followed by a package version, like following: "crosvm package version 0.1.0-123456". Sometimes, we need to know which exact version does a crosvm binary come from for developing and testing. It is useful if the git sha is built-in a crosvm binary. BUG=none TEST=PKG_VERSION=xxxxxx Cargo build && crosvm version TEST=PKG_VERSION=xxxxx emerge-eve crosvm && crosvm version TEST=./bin/fmt TEST=./bin/clippy TEST=./build_test.py --x86_64-sysroot /build/eve no errors reported and all behavor is as expected. v2: Refine version info. Change-Id: I89686dbe6ab2888d8a6ce5752a37241b4c00160d Signed-off-by: Yi Sun <yi.sun@intel.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1989256 Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
Diffstat (limited to 'disk')
0 files changed, 0 insertions, 0 deletions