README.md
1 # Fluoride Bluetooth stack
2
3 ## Building and running on AOSP
4 Just build AOSP - Fluoride is there by default.
5
6 ## Building and running on Linux
7
8 Instructions for Ubuntu, tested on 14.04 with Clang 3.5.0 and 16.10 with Clang
9 3.8.0
10
11 ### Download source
12
13 ```sh
14 mkdir ~/fluoride
15 cd ~/fluoride
16 git clone https://android.googlesource.com/platform/system/bt
17 ```
18
19 Install dependencies (require sudo access):
20
21 ```sh
22 cd ~/fluoride/bt
23 build/install_deps.sh
24 ```
25
26 Then fetch third party dependencies:
27
28 ```sh
29 cd ~/fluoride/bt
30 mkdir third_party
31 cd third_party
32 git clone https://github.com/google/googletest.git
33 git clone https://android.googlesource.com/platform/external/aac
34 git clone https://android.googlesource.com/platform/external/libchrome
35 git clone https://android.googlesource.com/platform/external/libldac
36 git clone https://android.googlesource.com/platform/external/modp_b64
37 git clone https://android.googlesource.com/platform/external/tinyxml2
38 ```
39
40 And third party dependencies of third party dependencies:
41
42 ```sh
43 cd fluoride/bt/third_party/libchrome/base/third_party
44 mkdir valgrind
45 cd valgrind
46 curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/valgrind.h?format=TEXT | base64 -d > valgrind.h
47 curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/memcheck.h?format=TEXT | base64 -d > memcheck.h
48 ```
49
50 NOTE: If system/bt is checked out under AOSP, then create symbolic links instead
51 of downloading sources
52
53 ```
54 cd system/bt
55 mkdir third_party
56 cd third_party
57 ln -s ../../../external/aac aac
58 ln -s ../../../external/libchrome libchrome
59 ln -s ../../../external/libldac libldac
60 ln -s ../../../external/modp_b64 modp_b64
61 ln -s ../../../external/tinyxml2 tinyxml2
62 ln -s ../../../external/googletest googletest
63 ```
64
65 ### Generate your build files
66
67 ```sh
68 cd ~/fluoride/bt
69 gn gen out/Default
70 ```
71
72 ### Build
73
74 ```sh
75 cd ~/fluoride/bt
76 ninja -C out/Default all
77 ```
78
79 This will build all targets (the shared library, executables, tests, etc) and
80 put them in out/Default. To build an individual target, replace "all" with the
81 target of your choice, e.g. ```ninja -C out/Default net_test_osi```.
82
83 ### Run
84
85 ```sh
86 cd ~/fluoride/bt/out/Default
87 LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride
88 ```
89
90 ### Eclipse IDE Support
91
92 1. Follows the Chromium project
93 [Eclipse Setup Instructions](https://chromium.googlesource.com/chromium/src/+/master/docs/linux_eclipse_dev.md)
94 until "Optional: Building inside Eclipse" section (don't do that section, we
95 will set it up differently)
96
97 2. Generate Eclipse settings:
98
99 ```sh
100 cd system/bt
101 gn gen --ide=eclipse out/Default
102 ```
103
104 3. In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML
105 location under system/bt/out/Default
106
107 4. Right click on the project. Go to Preferences->C/C++ Build->Builder Settings.
108 Uncheck "Use default build command", but instead using "ninja -C out/Default"
109
110 5. Goto Behaviour tab, change clean command to "-t clean"
111
112