commit | c501080f9163072f632530ac2a64c513aed109e7 | [log] [tgz] |
---|---|---|
author | Primiano Tucci <primiano@google.com> | Fri Jan 19 17:13:21 2018 +0000 |
committer | Primiano Tucci <primiano@google.com> | Fri Jan 19 18:56:28 2018 +0000 |
tree | b0cb2c80519badd9da861e49098cccc0c45640ec | |
parent | 3d5e7e672583bd8a20c4429045638b5283ab97b3 [diff] |
Generate merged trace config for use in the Android tree This solves two problems: 1) Including > 1 .proto from the android tree is too complex due to the unusual way protoc handles relative include paths (foo/../external/proto.proto and external/proto.proto are considered distinct and then collide on multiple redefinitions). 2) We really don't want to expose the datasource-specific config to the rest of the tree. That causes just unnecessary mainteinance pain when trying to add new DataSourceConfig(s). Bug: 71743564 Change-Id: I53f83ff69cc70a56f0d72383cac238100b554273
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