commit | ff48ce87cd192ff7df92bc666ff5c7d38ad3a005 | [log] [tgz] |
---|---|---|
author | Ajay Panicker <apanicke@google.com> | Thu Sep 20 14:39:00 2018 -0700 |
committer | Ajay Panicker <apanicke@google.com> | Mon Nov 05 11:47:43 2018 -0800 |
tree | d71f9168eb598ed75f4bc9e53064fa4bcbcab355 | |
parent | 90fd7638eb5deac2ead320ed76ac8a195969ba04 [diff] |
Add code coverage report support to Bluetooth Allow the generation of code coverage reports for any code that has native tests. In order to add coverage support to code do the following steps. 1. Add "clang_file_coverage" as a default to the source library(s) you want statistics for. 2. Add "clang_coverage_bin" as a default to the host supported test. 3. Add the test name and the files you want covered to "gen_coverage.py" - The files covered can either be a directory or files. - Avoid using / at the beginning of a covered file/dir as this breaks how the coverage generator resolves filenames. Bug: 114751344 Test: run ./gen_coverage.py and test arguments manually Change-Id: I9dd04f6ee2fd642531e301e3bfd52713f862cd4b
Just build AOSP - Fluoride is there by default.
Instructions for Ubuntu, tested on 14.04 with Clang 3.5.0 and 16.10 with Clang 3.8.0
mkdir ~/fluoride cd ~/fluoride git clone https://android.googlesource.com/platform/system/bt
Install dependencies (require sudo access):
cd ~/fluoride/bt build/install_deps.sh
Then fetch third party dependencies:
cd ~/fluoride/bt mkdir third_party cd third_party git clone https://github.com/google/googletest.git git clone https://android.googlesource.com/platform/external/aac git clone https://android.googlesource.com/platform/external/libchrome git clone https://android.googlesource.com/platform/external/libldac git clone https://android.googlesource.com/platform/external/modp_b64 git clone https://android.googlesource.com/platform/external/tinyxml2
And third party dependencies of third party dependencies:
cd fluoride/bt/third_party/libchrome/base/third_party mkdir valgrind cd valgrind curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/valgrind.h?format=TEXT | base64 -d > valgrind.h curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/memcheck.h?format=TEXT | base64 -d > memcheck.h
NOTE: If system/bt is checked out under AOSP, then create symbolic links instead of downloading sources
cd system/bt mkdir third_party cd third_party ln -s ../../../external/aac aac ln -s ../../../external/libchrome libchrome ln -s ../../../external/libldac libldac ln -s ../../../external/modp_b64 modp_b64 ln -s ../../../external/tinyxml2 tinyxml2 ln -s ../../../external/googletest googletest
cd ~/fluoride/bt gn gen out/Default
cd ~/fluoride/bt ninja -C out/Default all
This will build all targets (the shared library, executables, tests, etc) and put them in out/Default. To build an individual target, replace "all" with the target of your choice, e.g. ninja -C out/Default net_test_osi
.
cd ~/fluoride/bt/out/Default LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride
Follows the Chromium project Eclipse Setup Instructions until "Optional: Building inside Eclipse" section (don't do that section, we will set it up differently)
Generate Eclipse settings:
cd system/bt gn gen --ide=eclipse out/Default
In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML location under system/bt/out/Default
Right click on the project. Go to Preferences->C/C++ Build->Builder Settings. Uncheck "Use default build command", but instead using "ninja -C out/Default"
Goto Behaviour tab, change clean command to "-t clean"