CodeLite

codelite.org ↗

A cross-platform IDE for C, C++, Rust, PHP, and Node.js projects with filesystem workspaces and integrated debugging.

SI Score
80/100
Pricing
Free AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about CodeLite

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the CodeLite homepage

What it does

CodeLite is a desktop IDE for editing, building, and debugging C, C++, Rust, PHP, and Node.js code. Its File System Workspace can map an existing directory into a navigable tree instead of requiring every file to be added to a project by hand. Code completion, Git integration, build targets, and debugger views bring common tasks into one application. It is aimed at developers who want a configurable native IDE, especially for existing C-family codebases.

Bring an existing tree into the IDE

For a repository that already has its own build files, the official guide describes a File System Workspace. Choose File > New > New workspace, select File System Workspace, and point it at the source directory. CodeLite fills the tree from the filesystem, so you can browse a large codebase without manually registering each file. The workspace can also set file extensions and excluded paths for code completion and find-in-files operations.

This workspace is a view of real files, not a disposable project model: the guide says actions in its tree are applied to the filesystem. Treat delete and move operations accordingly. You can set an executable, working directory, arguments, toolchain, debugger, and build targets in workspace settings. A build target runs its configured command; it does not supply the compiler or project build configuration for you.

Inspect a debug session

For a C or C++ bug, an illustrative workflow is to configure the project executable and GDB, set a breakpoint at the suspicious function, and inspect locals and the call stack when execution stops. CodeLite's GDB guide documents a Debugger View with Locals, Watches, Call stack, Breakpoints, Threads, Memory, Output, and Disassemble tabs. It lists F9 for a line breakpoint, F10 to step over, and F11 to step into. These are documented controls, not results from a hands-on run.

The product is free and the project identifies GPLv2 as its license, with an exception for independently developed plugins. Check the license of any plugin you distribute; the IDE's stated exception does not replace a plugin's own terms.

Strengths

  • A File System Workspace automatically reflects an existing directory tree and can exclude paths or file extensions from code-completion and search operations.
  • The GDB integration documents locals, watches, call stacks, breakpoints, threads, memory, and stepping controls in one debugger view.
  • The official site lists Windows, Ubuntu/Linux, macOS, and FreeBSD downloads and names several languages supported by the IDE.

Watch out for

  • A File System Workspace applies tree operations to real files and folders, so moving or deleting items there changes the filesystem rather than only IDE metadata.

Best for

  • C and C++ developers who want to inspect and debug an existing source tree
  • Developers maintaining native or backend projects who need a configurable desktop editor, build target, and debugger

Sources