Debugging PMDO: Difference between revisions

From PMDOWiki
Shitpost Sunkern (talk | contribs)
No edit summary
Shitpost Sunkern (talk | contribs)
No edit summary
Line 38: Line 38:
# In the <code>Run and Debug</code> tab in VSCode, you can click on the green arrow to begin debugging.</br>[[File:Debug_Mac_VSCode_Debug.png|frameless]]
# In the <code>Run and Debug</code> tab in VSCode, you can click on the green arrow to begin debugging.</br>[[File:Debug_Mac_VSCode_Debug.png|frameless]]


[[Category: Framework]]
[[Category: Engine]]

Revision as of 05:10, 29 November 2022

PMDO Mac Debug Setup

Note: This has only been tested with Jetbrains Rider and Visual Studio Code

Made by: Trio-#4442

  1. Download .NET 5.0 https://dotnet.microsoft.com/en-us/download/dotnet/5.0. Confirm that it is installed using the command dotnet --list-runtimes.
  2. Recursively clone the PMDO repository using git clone --recurse-submodules -j8 https://github.com/audinowho/PMDODump.git.
  3. Copy all of the .dylib files in PMDC/PMDC/runtimes folders to PMDC/PMDC. Here’s what your file structure should look like:
  4. In your ~/.gitignore_global file, add the following files for git to ignore:
# Debug logs (npm, yarn)
*.log

# Editor artifacts
.*.sw[a-z]
*~
.#*
.vscode
.idea

# OS files
Thumbs.db
.DS_Store

You may want to include more. Modified from here.

The following steps below depend on your IDE of choice. See each section below.

Jetbrains Rider

Jetbrains Rider requires a paid subscription.

  1. Debug should run out of the box. Set the configuration to PMDC and click "Debug", and you should be all ready to go!

Visual Studio Code

  1. Install the C# extension. There is a possibility that you have to downgrade to an older version like v1.24.4 or modify the settings in Omnisharp settings discussed here? But I personally wasn’t able to figure out how to make it work.
  2. Create .vscode/launch.json in the root folder of PMDODump In launch.json, copy everything from here to the file.
  3. In the Run and Debug tab in VSCode, you can click on the green arrow to begin debugging.