vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-06 19:40:10 +02:00
Code Issues Packages Projects Releases Wiki Activity

Remove all references to Boost

Browse Source 
Since we no longer depend on any of it.
This commit is contained in:
Robbert van der Helm
2022-04-15 15:25:03 +02:00
parent 7b3afa4043
commit 88ac466501
7 changed files with 16 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture.md
+3 -3
View File
@@ -61,9 +61,9 @@ interacts with the Win32 message loop or the GUI has to be done from the same
thread (or typically the main thread). To do this yabridge will execute certain
'unsafe' functions that are likely to interact with these things from the main
thread. The main thread also periodically handles Win32 and optionally also X11
events (when there are open editors) using a Boost.Asio timer, so these function
calls can all be done from that same thread by posting a task to the Boost.Asio
IO context.
events (when there are open editors) using an Asio timer, so these function
calls can all be done from that same thread by posting a task to the Asio IO
context.
On the native Linux side it usually doesn't matter which thread functions are
called from, but since REAPER does not allow any function calls that interact