You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sandy 5629dff5f1 PL280 release code 4 years ago
..
audio_a2dp_hw PL280 release code 4 years ago
audio_bluetooth_hw PL280 release code 4 years ago
audio_hal_interface PL280 release code 4 years ago
audio_hearing_aid_hw PL280 release code 4 years ago
binder PL280 release code 4 years ago
bta PL280 release code 4 years ago
btcore PL280 release code 4 years ago
btif PL280 release code 4 years ago
build PL280 release code 4 years ago
common PL280 release code 4 years ago
conf PL280 release code 4 years ago
device PL280 release code 4 years ago
doc PL280 release code 4 years ago
embdrv PL280 release code 4 years ago
gd PL280 release code 4 years ago
hci PL280 release code 4 years ago
include PL280 release code 4 years ago
internal_include PL280 release code 4 years ago
linux_include/log PL280 release code 4 years ago
main PL280 release code 4 years ago
mediatek PL280 release code 4 years ago
osi PL280 release code 4 years ago
packet PL280 release code 4 years ago
profile PL280 release code 4 years ago
proto PL280 release code 4 years ago
service PL280 release code 4 years ago
stack PL280 release code 4 years ago
test PL280 release code 4 years ago
tools PL280 release code 4 years ago
types PL280 release code 4 years ago
udrv PL280 release code 4 years ago
utils PL280 release code 4 years ago
vendor_libs PL280 release code 4 years ago
vnd PL280 release code 4 years ago
.clang-format PL280 release code 4 years ago
.gn PL280 release code 4 years ago
Android.bp PL280 release code 4 years ago
AndroidTestTemplate.xml PL280 release code 4 years ago
BUILD.gn PL280 release code 4 years ago
CleanSpec.mk PL280 release code 4 years ago
EventLogTags.logtags PL280 release code 4 years ago
MODULE_LICENSE_APACHE2 PL280 release code 4 years ago
NOTICE PL280 release code 4 years ago
OWNERS PL280 release code 4 years ago
PREUPLOAD.cfg PL280 release code 4 years ago
README.md PL280 release code 4 years ago
TEST_MAPPING PL280 release code 4 years ago

README.md

Fluoride Bluetooth stack

Building and running on AOSP

Just build AOSP - Fluoride is there by default.

Building and running on Linux

Instructions for Ubuntu, tested on 14.04 with Clang 3.5.0 and 16.10 with Clang 3.8.0

Download source

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

Generate your build files

cd ~/fluoride/bt
gn gen out/Default

Build

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.

Run

cd ~/fluoride/bt/out/Default
LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride

Eclipse IDE Support

  1. Follows the Chromium project Eclipse Setup Instructions until "Optional: Building inside Eclipse" section (don't do that section, we will set it up differently)

  2. Generate Eclipse settings:

cd system/bt
gn gen --ide=eclipse out/Default
  1. In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML location under system/bt/out/Default

  2. 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"

  3. Goto Behaviour tab, change clean command to "-t clean"