I'm using environment variables for this, and you can set these up however you like, as long as they'll be defined in an environment that VS Code executes in. Once CMake, Visual Studio Code + Extensions are setup and everything is unpacked to where they're supposed to be, we need to setup an environment with which that would allow our setup to work. This essentially defines our toolchain to cmake. There is also the "arm_patched.cmake" file, place that in (Playdate SDK)/C_API/buildsupport. This zip holds a template workspace folder called "c_template", which is already setup to be working with VSCode when your environment is setup properly. Again, this will be going into its own environment variable.Īddtional Helper Files vscode_helpers_v2.zip (3.8 KB) If you haven't already unpacked this, go on and do it! Be sure to note the path where "bin" is a child directory. We will save the path in a new environment variable later. C:/playdate_dev/arm_toolchain) and note the path. GCC ARM Toolchain ( Arm GNU Toolchain | 9-2019-q4-major – Arm Developer)Īs we did with Ninja, unpack the zip into some directory (for ex.
This would be done so CMake Tools would be able to use it. Remember where you put it, we're gonna need to add it to our PATH environment variable later.
Just unpack this in some directory (for ex. We use CMake because Panic has provided some helper CMake files that help generate/compile our project, and Visual Studio Code as it has extensions to interact with CMake.įirst half of our build system this will configure and generate Ninja build files for us to build our project with.ĭon't forget the extensions! They help us get Visual Studio Code to a decently functioning IDE for our project. This will setup a simple C project using Visual Studio Code and CMake. Also, none of this is really Windows only, the modified bits are fixed up to also support Windows properly as well as allow user defined paths for the SDK and toolchain using environment variables.
Setup c in visual studio code how to#
The SDK for Windows is a little anemic, so I figured this might be useful to anyone trying to figure out how to program in C on Windows.
0 kommentar(er)
