commit | 071b507ad4278ae1ad24a188144d18cddf1b7137 | [log] [tgz] |
---|---|---|
author | Jack He <siyuanh@google.com> | Tue Feb 07 17:25:15 2017 -0800 |
committer | Jack He <siyuanh@google.com> | Thu Feb 09 14:44:41 2017 -0800 |
tree | 10ae9c1f55b7bf57ecbc095987a81ae5eef1942f | |
parent | 82fc2a96ef7858a086211c780a047d7ab54ba123 [diff] |
Use same timestamp for on-disk BT Snoop Log and in-memory BT Snooz Log * Logcat uses gettimeofday for its timestamp, the same as on-disk BT Snoop log * Although in-memory BT Snooz Log uses the same method to get time, it is calling it separately, resulting in mismatch between timestamps of two snoop logs * This CL let them uses the same timestamp_us value and put the function definition to libosi * Note that preserved on-disk BT Snoop logs timestamp postfix at btsnoop_hci_<timestamp>.log will be changed to microsecond since epoch at current device timezone instead of the shifted BT Snoop timestamp value * New unit tests for gettimeofday Bug: 35113514 Test: Make, unit tests, run BT activities and check both snoop logs Change-Id: I5b3f87bc523b272ced2c69a4595d0e0cbe29bcb3
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/libchrome 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/libchrome libchrome 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"