commit | 3e01e01305f0adfd49571499d884514d966a9049 | [log] [tgz] |
---|---|---|
author | Pavlin Radoslavov <pavlin@google.com> | Fri Apr 06 17:05:47 2018 -0700 |
committer | Pavlin Radoslavov <pavlin@google.com> | Wed Apr 11 18:19:32 2018 +0000 |
tree | 48bd42779a49ab68563a37826b3cc68d317908a9 | |
parent | 37ddd18526addeabd72ce0a2007caeab3e880aae [diff] |
Improve A2DP codec run-time debug-abilitity Rename A2DP_DumpCodecInfo() to A2DP_CodecInfoString() and change the usage. Previously, A2DP_DumpCodecInfo() would print the the codec information only if LOG_VERBOSE() was enabled in compile time. The new A2DP_CodecInfoString() now returns human-readable std::string with the codec information. That string can be used in debug log messages that can be enabled in run-time. Bug: 77525584 Test: Manual - Examine log messages when A2DP streaming with and without debug log messages enabled. Change-Id: Idd440d6c9e908520132feeeb5388d3e6aefa26db Merged-In: Idd440d6c9e908520132feeeb5388d3e6aefa26db (cherry picked from commit 25cd05412d18c67b1f0e1f4e07a8178029c0ff0c)
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”