commit | 0a7d0bdbdfbc566c0bb23b8e63200028153210f3 | [log] [tgz] |
---|---|---|
author | Ajay Panicker <apanicke@google.com> | Wed Sep 06 09:59:51 2017 -0700 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Fri Sep 22 23:20:27 2017 +0000 |
tree | 0ae12e9585d95efbbed28a55b7eaa5ae3ab10fa5 | |
parent | b6291d482af5a775f05f0996fbf04884fc9ac01f [diff] |
Change our AVRCP capabilities if the remote device only supports 1.3 This prevents issues with devices that only support 1.3 but can not handle forward compatability like some Alpine Carkits. Bug: 37943083 Test: Connect to Alpine carkit that only supports 1.3 and see new features are used. Change-Id: I6d041590dc51d7e8711b17fb1cb9c880b640052a Merged-In: I6d041590dc51d7e8711b17fb1cb9c880b640052a (cherry picked from commit f9f1c8b449efb9cb7894a64fe2977f875679ba52) (cherry picked from commit ff2d86ed3af91099597d033a76a143437543d6fd) (cherry picked from commit c8ab11a06a6d4c4a37184fe9be655e560d3a340d)
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 git clone https://android.googlesource.com/platform/hardware/libhardware
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 ../../../hardware/libhardware libhardware 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”