commit | 4b2386969f18ae46ea8699c05b1f5ae20382c6ad | [log] [tgz] |
---|---|---|
author | Charlie Boutier <charliebout@google.com> | Thu Aug 11 00:44:44 2022 +0000 |
committer | Android (Google) Code Review <android-gerrit@google.com> | Thu Aug 11 00:44:44 2022 +0000 |
tree | 6ce93aa9fe3103b359d5f654ccb5b31d0636f472 | |
parent | c3bc8ada1953057e8feea0afff5b3b7e03ae1fa1 [diff] | |
parent | 96644962ccf017794bd71a99a431467b3cbd0773 [diff] |
Merge changes from topic "aosp_master_pandora_cherry_pick" into tm-qpr-dev * changes: Move from libbacktrace libunwindstack. RootCanal: Add Link to Link Manager when connection is created Revert "RootCanal: Use weak_ptr for Phy, Device" Fix crash in emulator unit tests Mark a few bluetooth unit tests as isolated:false RootCanal: Use weak_ptr for Phy, Device RootCanal: Only remove BR_EDR links from LMP rootcanal: correctly handle error conditions in test command add_phy. RootCanal: Implement LMP as a rust library Root-Canal: Generate LE_Channel_Selection_Algorithm event RootCanal: Fix hci sniffer packet direction endianness RootCanal: Extract pcap writing logic outside hci_sniffer Enable sniffing of HCI packets to std::ostream RootCanal: Add a HciSniffer PTS-bot: update list of PTS-bot tests Added list instance removal in GattInstance#disconnect() [PANDORA_TEST] pts-bot HFP Coverage: TCA [PANDORA_TEST] Update a2dp method to use a device [PANDORA_TEST] pts-bot HFP Coverage: WBS [PANDORA_TEST] Update host method to use a device PTS bot implementation for GATT profile tests RootCanal: Set HCI Version in controller_properties to 5.3 [PANDORA_DEV] Allow Bluetooth hidden from Pandora [PANDORA_TEST] Implement SMP test on pts-bot Pandora: Add SDP/SR/ support Add a pre-test mmi to get the pts address [PANDORA_TEST] pts-bot HFP Coverage: HFI & SLC [PANDORA] Remove Shadowing since we now can call hidden Escape MMIs that are not Python identifiers [PANDORA_TEST] pts-bot HFP Coverage: DIS/BV-01-I Pandora: Remove warnings from deprecated functions Pandora: Skip AVDTP/SRC/INT/SIG/SMG/BI-35-C PTS-bot: fix failure during reset PTS-bot: fix failure after reset PTS-bot: remove A2DP/SUS/ tests PTS-bot: Build AudioTrack at first Start PTS-bot: fix reset PTS-bot: fix AVDTP/SRC/INT/SIG/SMG/BV-17-C PTS-bot: freeze protobuf python package [LSC] Add LOCAL_LICENSE_KINDS to packages/modules/Bluetooth PTS-bot: add default timeout and AVDTP tests PTS-bot: global configuration Pandora: Add mmi2grpc [PTS-BOT] stop skipping A2DP/SRC/CC/BV-09-I [PTS-BOT] Sort pts config PTS-bot: add PTS-bot in general tests PandoraServer: Synchronize AudioTrack writes Pandora: Rename all references of Blueberry to Pandora Pandora: Rename Blueberry folder to Pandora
Just build AOSP - Fluoride is there by default.
Instructions for a Debian based distribution:
You'll want to download some pre-requisite packages as well. If you're currently configured for AOSP development, you should have most required packages. Otherwise, you can use the following apt-get list or use the --run-bootstrap
option on build.py
(see below) to get a list of packages missing on your system:
sudo apt-get install repo git-core gnupg flex bison gperf build-essential \ zip curl zlib1g-dev gcc-multilib g++-multilib \ x11proto-core-dev libx11-dev libncurses5 \ libgl1-mesa-dev libxml2-utils xsltproc unzip liblz4-tool libssl-dev \ libc++-dev libevent-dev \ flatbuffers-compiler libflatbuffers1 openssl \ libflatbuffers-dev libtinyxml2-dev \ libglib2.0-dev libevent-dev libnss3-dev libdbus-1-dev \ libprotobuf-dev ninja-build generate-ninja protobuf-compiler \ libre2-9 debmake \ llvm libc++abi-dev \ libre2-dev libdouble-conversion-dev
You will also need a recent-ish version of Rust and Cargo. Please follow the instructions on Rustup to install a recent version.
mkdir ~/fluoride cd ~/fluoride git clone https://android.googlesource.com/platform/packages/modules/Bluetooth
build.py
is the helper script used to build Fluoride for Linux (i.e. Floss). It accepts a --run-bootstrap
option that will set up your build staging directory and also make sure you have all required system packages to build (should work on Debian and Ubuntu). You will still need to build some unpackaged dependencies (like libchrome, modp_b64, googletest, etc).
To use it:
./build.py --run-bootstrap
This will install your bootstrapped build environment to ~/.floss
. If you want to change this, just pass in --bootstrap-dir
to the script.
The following third-party dependencies are necessary but currently unavailable via a package manager. You may have to build these from source and install them to your local environment.
We provide a script to produce debian packages for those components. Please see the instructions in build/dpkg/README.txt for more details.
cd system/build/dpkg mkdir -p outdir/{modp_b64,libchrome} # Build and install modp_b64 pushd modp_b64 ./gen-src-pkg.sh $(readlink -f ../outdir/modp_b64) popd sudo dpkg -i outdir/modp_b64/*.deb # Build and install libchrome pushd libchrome ./gen-src-pkg.sh $(readlink -f ../outdir/libchrome) popd sudo dpkg -i outdir/libchrome/*.deb
The googletest packages provided by Debian/Ubuntu (libgmock-dev and libgtest-dev) do not provide pkg-config files, so you can build your own googletest using the steps below:
git clone https://github.com/google/googletest.git -b release-1.10.0 cd googletest # Main directory of the cloned repository. mkdir build # Create a directory to hold the build output. cd build cmake .. # Generate native build scripts for GoogleTest. sudo make install -DCMAKE_INSTALL_PREFIX=/usr # Optional steps if pkgconfig isn't installed to desired location # Modify the source (/usr/lib/x86_64-linux-gnu) and target (/usr/lib) based on # your local installation. for f in $(ls /usr/lib/x86_64-linux-gnu/pkgconfig/{gtest,gmock}*); do \ ln -sf $f /usr/lib/pkgconfig/$(basename $f); done
Note: Handled by --run-bootstrap
option.
Run the following to install Rust dependencies:
cargo install cxxbridge-cmd
Note: Handled by --run-bootstrap
option.
For host build, we depend on a few other repositories:
Clone these all somewhere and create your staging environment.
export STAGING_DIR=path/to/your/staging/dir mkdir ${STAGING_DIR} mkdir -p ${STAGING_DIR}/external ln -s $(readlink -f ${PLATFORM2_DIR}/common-mk) ${STAGING_DIR}/common-mk ln -s $(readlink -f ${PLATFORM2_DIR}/.gn) ${STAGING_DIR}/.gn ln -s $(readlink -f ${RUST_CRATE_DIR}) ${STAGING_DIR}/external/rust ln -s $(readlink -f ${PROTO_LOG_DIR}) ${STAGING_DIR}/external/proto_logging
We provide a build script to automate building assuming you've staged your build environment already as above. At this point, make sure you have all the pre-requisites installed (i.e. bootstrap option and other dependencies above) or you will see failures. In addition, you may need to set a --libdir=
if your libraries are not stored in /usr/lib
by default.
./build.py
This will build all targets to the output directory at --bootstrap-dir
(which defaults to ~/.floss
). You can also build each stage separately (if you want to iterate on something specific):
You can choose to run only a specific stage by passing an arg via --target
.
Currently, Rust builds are a separate stage that uses Cargo to build. See gd/rust/README.md for more information. If you are iterating on Rust code and want to add new crates, you may also want to use the --no-vendored-rust
option (which will let you use crates.io instead of using a pre-populated vendored crates repo).
By default on Linux, we statically link libbluetooth so you can just run the binary directly. By default, it will try to run on hci0 but you can pass it --hci=N, where N corresponds to /sys/class/bluetooth/hciN.
$OUTPUT_DIR/debug/btadapterd --hci=$HCI INIT_gd_hci=true