| commit | 692f8cf84e5149e3ce61412f07e0b8e9f46aa57b | [log] [tgz] |
|---|---|---|
| author | Przemyslaw Pietrzkiewicz <ppi@chromium.org> | Wed Jun 17 15:22:31 2015 +0200 |
| committer | Przemyslaw Pietrzkiewicz <ppi@chromium.org> | Wed Jun 17 15:22:31 2015 +0200 |
| tree | 0838b86567afc8e1e669e06ae40b489546d1811b | |
| parent | 8ba52844ca3602bd742a32d5d78d4931579ab679 [diff] |
Move android_stack_parser to devtools, adapt and hook it up in `debugger`. To try it, run: mojo/devtools/common/debugger device awsnap for Chromium-style checkouts (e.g. Mojo) with build in out/android_Debug this doesn't require any further arguments - regardless of where devtools are checked in, as long as they are somewhere under the checkout root. One can set --build-dir and --ndk-dir for non-standard setups. See #238. R=etiennej@chromium.org Review URL: https://codereview.chromium.org/1186113002. Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 188e070f0201c70ddeec63a295cc9ce83df25bda
Unopinionated tools for running, debugging and testing Mojo apps.
The repo consists of:
As devtools carry no assumptions about build system or file layout being used, the primary way of using devtools now is to embed the functionality provided by devtoolslib in a thin wrapper script. For examples, one can refer to mojo's shell runner and apptest runner.
The set of executable scripts is WIP. We currently offer:
git clone https://github.com/domokit/devtools.git
The library is canonically developed in the mojo repository, https://github.com/domokit/devtools is a mirror allowing to consume it separately.