mirror of
https://github.com/bluekitchen/btstack.git
synced 2025-03-24 04:43:36 +00:00
doc: mention qt run loop integration
This commit is contained in:
parent
0a8d3146f2
commit
1e5045638b
@ -35,7 +35,7 @@ Currently, we have two examples for this:
|
||||
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.
|
||||
|
||||
- *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
|
||||
implemented in terms of CoreFoundation calls, data sources and
|
||||
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
|
||||
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}
|
||||
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user