badlogic / vscode-dos-dev-extension

Visual Studio Code DOS development extension
MIT License
30 stars 3 forks source link

Windows 10 build and attach issues #4

Open ChristopherDrum opened 1 year ago

ChristopherDrum commented 1 year ago

Running

Couldn't get VSC to connect to dosbox-x in Debug build. dosbox-x always sat at "Waiting for debugger" indefinitely. Couldn't get VSC to launch dosbox-x in Release build whatsoever. Same extension works fine on macOS out of the box, so I did some digging.

Discovered the following 3 issues (though only 2 are really actionable):

  1. In launch.json "command": ".vscode/run-windows.bat ${userHome} ${command:cmake.getLaunchTargetPath}; exit", does not work. Console errors with "'.vscode' is not recognized as an internal or external command". Resolved by moving run-windows.bat to the main project directory and not inside a . folder.
  2. In launch.json "target: localhost:5123", seems to be where Debug build can't connect to dosbox-x. Resolved by setting "target: 0.0.0.0:5123" (ran dosbox-x then checked netstat -bano and saw that it isn't running under 127.0.0.1)
  3. Couldn't get Release build to run when I had a space in the folder path. (test project is a subfolder inside a main folder named DOS Projects) Resolved by renaming parent (grandparent?) folder to dos_projects (saw in console it logged a non-escaped path to the built .exe file)