doc: mention qt run loop integration

This commit is contained in:
Matthias Ringwald 2020-03-02 10:05:01 +01:00
parent 0a8d3146f2
commit 1e5045638b

View File

@ -35,7 +35,7 @@ Currently, we have two examples for this:
managed in a linked list. Then, the *select* function is used to wait managed in a linked list. Then, the *select* function is used to wait
for the next file descriptor to become ready or timer to expire. for the next file descriptor to become ready or timer to expire.
- *btstack_run_loop_cocoa.c* is an implementation for the CoreFoundation - *btstack_run_loop_cocoa.c* is an integration for the CoreFoundation
Framework used in OS X and iOS. All run loop functions are Framework used in OS X and iOS. All run loop functions are
implemented in terms of CoreFoundation calls, data sources and implemented in terms of CoreFoundation calls, data sources and
timers are modeled as CFSockets and CFRunLoopTimer respectively. timers are modeled as CFSockets and CFRunLoopTimer respectively.
@ -45,6 +45,11 @@ Currently, we have two examples for this:
Then, the *WaitForMultipleObjects* is used to wait for the next Event to Then, the *WaitForMultipleObjects* is used to wait for the next Event to
becomre ready or timer to expire. becomre ready or timer to expire.
- *btstack_run_loop_qt* is an integration for the Qt run loop.
The data sources on Windows systems use Event objects via Qt's QEventNotifier adapter,
while a QSocketNotifier is used for Mac/Linux to handle file descriptors.
With these in place, the Windows/POSIX implemenations for HCI USB/H2 and HCI H4 can be used.
## Adapting BTstack for Multi-Threaded Environments {#sec:multithreadingIntegration} ## Adapting BTstack for Multi-Threaded Environments {#sec:multithreadingIntegration}