docs/api-reference/bluetooth/index.rst

Bluetooth API
*************

.. toctree::
   :maxdepth: 2

   Bluetooth Controller && VHCI <controller_vhci>
   Bluetooth Common <bt_common>
   Bluetooth LE <bt_le>
   Bluetooth Classic BT <classic_bt>


Example code for this API section is provided in :example:`bluetooth` directory of ESP-IDF examples.
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00			`Bluetooth API`
			`*************`
API template - reflected template in other DRAFT API dcouments - DRAFT of Bluetooth API - link fixes in CONTRIBUTING.rst 2016-10-26 21:08:36 +02:00
component/bt : doxygen can generate html correctly 2016-12-01 20:20:22 +08:00			`.. toctree::`
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00			`:maxdepth: 2`
API template - reflected template in other DRAFT API dcouments - DRAFT of Bluetooth API - link fixes in CONTRIBUTING.rst 2016-10-26 21:08:36 +02:00
component/bt: modify bluetooth API 1. VHCI api and doxygen 2. Controller api and doxygen 3. bluedroid init/enable api and doxygen 4. cleanup demo codes 2017-01-03 15:53:06 +08:00			`Bluetooth Controller && VHCI <controller_vhci>`
component/bt : doxygen can generate html correctly 2016-12-01 20:20:22 +08:00			`Bluetooth Common <bt_common>`
			`Bluetooth LE <bt_le>`
component/bt: clean up the API header and generate documentation files 2017-03-18 14:55:31 +08:00			`Bluetooth Classic BT <classic_bt>`
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00
Added links from api category TOC to example category folders Typo fix in bluetooth README.md 2017-01-18 21:04:11 +01:00
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests. 2017-01-19 16:16:06 +08:00			Example code for this API section is provided in :example:`bluetooth` directory of ESP-IDF examples.