vscode builds #238
samiam95124
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Building with vscode
Under the .vscode directory, tasks.json, a simple formula now exists to build the file currently selected in the vscode editor. This is done by hitting:
ctrl-shift-B
or
Terminal->Run Build Task (at the top left menu)
For build.
How it works
The pc or compiler integrator greatly simplifies building, so the line:
pc
Usually suffices to build a program or module. Thus, executing a build in vscode just executes that line with the current file selected.
What you need
> codeWithin a shell that has ./bin/pc on its $PATH variable.
Running with debug (gdb)[1]
I'm still working on this one. Watch this thread.
Running with pint (debugger)
This is also possible but more complex. I expect sometime in the future.
[1] It actually works, its just braindead, and has no advantage over just executing under gdb. I set up the experiment as a parallel to running a C program, that is, the same run conditions as an equivalent C program. I expected that vs code would present the same controlability as the C program, that is, ability to set source breakpoints and have the go/step/stepi, etc interface. vscode has all of the data it needs to do it, but is perhaps keying off the filename to suppress it, ie., .c extension.
Beta Was this translation helpful? Give feedback.
All reactions