commit | 273823c477ec4a65e4b6b3638defa21673fe790f | [log] [tgz] |
---|---|---|
author | Hector Dearman <hjd@google.com> | Fri Oct 13 18:12:27 2017 +0100 |
committer | Hector Dearman <hjd@google.com> | Fri Oct 13 18:12:27 2017 +0100 |
tree | 823a7ff411903b5ec28b48ad743d4bd4acde3a27 | |
parent | 7864876cd41b06e46ba351a0d3b31f5111c4f18c [diff] |
Wait for emulator to boot before running tests We should wait for the emulator to finish booting before running tests to avoid flakes like: https://travis-ci.org/catapult-project/perfetto/builds/287228461 Bug: 67765711 Change-Id: I033a864d441f9e12d1aa4284aff385f44d50473a
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 build/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 build/
prefix below and just use gn/ninja from depot_tools.
$ build/install-build-deps
to install third-party build deps (NDK etc)
$ build/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)
$ build/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).
$ build/ninja -C out/default (libtracing_unittests | libtracing_benchmarks) $ out/default/libtracing_unittests --gtest_help
Either connect a device in ADB mode or use the bundled emulator.
To start the emulator:$ build/run_android_emulator (arm | arm64) &
To run the tests (either on the emulator or physical device):$ build/run_android_test out/default libtracing_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