| commit | a5ff2a8e5a4db1aa74dbe04ebf94a28f74cf665c | [log] [tgz] |
|---|---|---|
| author | Primiano Tucci <primiano@google.com> | Wed Dec 20 11:37:00 2017 +0100 |
| committer | Primiano Tucci <primiano@google.com> | Wed Dec 20 15:49:48 2017 +0000 |
| tree | 4db42ccc1655d2de0909c426b3fdfda717184b1d | |
| parent | bbaa58c526418f0a621d7fc8e85d73d168a7295a [diff] |
Wire up traced binary Also simplify a bit the include/ folder. Not sure we'll ever need more than one header. That the code under traced contains only leaf executables and not libraries, one hader for the two Main(s) should be sufficient. Also fixes static lib generation for Mac. Change-Id: I3e1fed0f02aef61b1cf797b89855b981e0d73a5e
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.
All dependent libraries are self-hosted and pulled by the tools/install-build-deps script.
The only requirements on the host are python, git and a compiler (preferably clang, gcc is maintained best-effort):$ sudo apt-get update && sudo apt-get install git clang python
Then:$ git clone https://android.googlesource.com/platform/external/perfetto.git
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.
If you are a chromium developer and have depot_tools installed you can avoid the tools/ prefix below and just use gn/ninja from depot_tools.
$ tools/install-build-deps to install third-party build deps (NDK etc)
$ tools/gn args out/android to generate build files and enter in the editor:
target_os = "android" # Leave empty for local testing target_cpu = "arm" or "arm64" # Only when building for Android
(See the Build Configurations section below for more)
$ tools/ninja -C out/android all
TODO. The plan is to autogenerate the Android.bp build files from the master GN build files (or temporarily maintain both until we can autogenerate them).
$ 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
The following GN args are supported:
target_os = "android" | "linux" | "mac":
Defaults to the current host, set “android” to build for Android.
target_cpu = "arm" | "arm64" | "x86" | "x64":
Defaults to "arm" when target_os == "android", "x64" when targeting the host. 32-bit host builds are not supported.
is_debug = true | false:
Toggles Debug (default) / Release mode.
is_clang = true | false:
Use Clang (default) / GCC. It requires clang 3.5+ to be installed on the host. Clang is the default compiler on Mac (% having installed Xcode). On Linux: sudo apt-get update && sudo apt-get install clang
cc = "gcc" / cxx = "g++":
Uses a different compiler binary (default: autodetected depending on is_clang).
is_asan = true:
Enables Address Sanitizer
is_lsan = true:
Enables Leak Sanitizer
(Linux/Mac only)
is_msan = true:
Enables Memory Sanitizer
(Linux only)
is_tsan = true:
Enables Thread Sanitizer
(Linux/Mac only)
is_ubsan = true:
Enables Undefined Behavior Sanitizer