You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,15 +76,13 @@ Look at the Unity-SDK.code-workspace setup for VSCode. This will use the Meet Sa
76
76
77
77
For C# debugging, there is a simple attach launch option called `C# Unity`, for example in the `Meet/.vscode/launch.json`.
78
78
79
-
For Rust / C++ debugging on MacOS, you need to install the [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) extension installed.
79
+
For Rust / C++ debugging on MacOS, you need to install the [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) extension. The debug attach is defined in `.vscode/launch.json`.
80
80
81
81
1. Build the livekit-ffi lib locally in debug mode with `./BuildScripts~/build_ffi_locally.sh macos debug`
82
82
2. Start the Unity Editor
83
-
3. Attach to the Unity Editor process
83
+
3. Attach to the Unity Editor process (either auto or manual process picker)
84
84
4. Start the Scene in Editor
85
85
86
-
For step 3. you can have a look at `.vscode/launch.json` to improve the process picking for your setup.
0 commit comments