| commit | 20b760c0fd3e6b5d753ee499c71122a5fd84518e | [log] [tgz] |
|---|---|---|
| author | Primiano Tucci <primiano@google.com> | Fri Jan 19 12:36:12 2018 +0000 |
| committer | Primiano Tucci <primiano@google.com> | Fri Jan 19 14:42:30 2018 +0000 |
| tree | 6d07e8e331a7c3aaa2383b90c9681d5dc4b0d90e | |
| parent | c2a38ea365bcc47939db5555af8d4298123d7371 [diff] |
Reshuffle .proto files under /proto This CL does the following: 1) Separates the proto files under three folders (config, trace, ipc). This allow to have distinct targets that the various clients can link in, without pulling in the rest. 2) Moves all the protos under a "perfetto" subdirectory. This is to reduce the ambiguity of the import statements within the .proto files themselves. Now all imports look like: import "perfetto/trace/trace.proto"; As a side effect this also means that both the perfetto public headers (i.e. the code under include/) and the generated protobufs are accessible as #include "perfetto/XXX". Change-Id: I05d13a7b720fe50edb078fc99758b0f58b8feabc
This project is meant to be built both as part of the Android tree and from a standalone checkout
For internal docs see this page
Android is the platform targeted in the first milestones. Right now Linux desktop and OSX are maintained best-effort.
This project uses Android AOSP Gerrit for code reviews and uses the Google C++ style. Currently targets -std=c++11.
You can use both git cl upload from Chromium depot tools or Android repo to upload patches.
git cl is quite convenient as it supports code auto-formatting via git cl format.
See https://source.android.com/source/contributing for more details about external contributions and CLA signing.
See docs/build_instructions.md
Continuous build and test coverage is available at perfetto-ci.appspot.com. Trybots: CLs uploaded to gerrit are automatically submitted to TravisCI within one minute and made available on the CI page above. The relevant code lives in the infra/ directory.
$ tools/ninja -C out/default (tracing_unittests | tracing_benchmarks) $ out/default/tracing_unittests --gtest_help
Either connect a device in ADB mode or use the bundled emulator.
To start the emulator:$ tools/run_android_emulator (arm | arm64) &
To run the tests (either on the emulator or physical device):$ tools/run_android_test out/default tracing_unittests