ashwani Up a Local C Environment

You need two things, not one

Writing C locally isn’t just “install an app and go.” There are really two separate pieces involved:

1. A text editor — something to actually write the C code in.
2. A compiler — the program that reads your C code and translates it into machine code your computer can run.

A lot of beginners get confused here because many languages they’ve used before (Python, JavaScript) run through an interpreter, so there’s no separate “compile” step they have to think about. C isn’t like that — your source code is useless to the computer until a compiler turns it into an actual executable.

Because setting up an editor and a compiler separately is annoying, most people use an IDE (Integrated Development Environment) instead — a single program that bundles both together, plus extra conveniences like error highlighting.

Picking a setup based on your OS

What you need depends on what you’re running:

The browser option is worth knowing about even if you don’t use it long-term: it’s useful for quickly testing a short snippet without touching your local setup at all. But for anything beyond a one-off test, a real local install is worth doing — it’s closer to how you’ll actually work on larger programs.

Why Code::Blocks (on Windows) specifically

Popular IDE/editor options for C include Code::Blocks, Visual Studio, and VS Code — all free, and all capable of finding errors in your code as you write. Code::Blocks tends to be recommended for beginners on Windows specifically because installing it also installs MinGW, which includes GCC (the actual compiler) bundled with the editor. That means one install gets you both pieces you need, instead of having to track down and configure a compiler separately.

On Linux, this is less of an issue since GCC is frequently preinstalled — worth checking with gcc --version before assuming you need to install anything at all.

Confirming it actually works

Once a compiler is in place, the real test is compiling and running something small — not just confirming the IDE opens. A minimal program like this is enough to prove the whole pipeline (editor → compiler → executable) is working end to end:

#include <stdio.h>

int main() {
    printf("Hello World!");
    return 0;
}

If that prints Hello World! after you compile and run it, the setup is good and you’re ready to move on to writing real programs instead of fighting the toolchain.