Getting started with Nebula

Installation

The fastest path is the Windows setup installer. After installation, open your project and run one full build so Nebula can collect the data needed for build analysis and file-level visibility.

1. 1. Download the Windows setup

   Start from the latest installer and complete the standard install flow.

2. 2. Open your C++ project

   Load a real workspace, validate the toolchain, and make sure the build can run inside Nebula.

3. 3. Run a first clean build

   Nebula becomes much more useful once it has a fresh view of compile cost, warnings, and source-to-header pressure.

1. Download Nebula for Windows
2. Install the setup
3. Open your C++ workspace
4. Run a full build inside Nebula

Code Map split

Code Map split is built for one of the hardest parts of C++ development: understanding why builds are slow. Nebula separates headers on the left and source files on the right, then annotates each file with compile cost, warnings, and errors.

Build visibility

Instead of parsing long build logs, you can quickly see which headers pollute too many translation units, which source files cost the most to compile, and where warnings accumulate.

• Heavy headers become obvious.
• Slow translation units stand out immediately.
• Refactor candidates become easier to prioritize.
• Compile time is visible at the file level.

Best use cases

Code Map split is most valuable on large C++ codebases where compile time, header pressure, and unclear file boundaries create daily friction.

• Large desktop applications.
• Game engines and simulation codebases.
• Embedded or tooling-heavy projects.
• Teams preparing build-focused refactors.

Troubleshooting

If the installer does not launch, retry after a page refresh and check local antivirus permissions. If build insights look incomplete, run a clean build so Nebula can rebuild its view of the project.

• If download fails, retry from the Windows setup page.
• If build analysis looks partial, run a full clean build.
• If something still breaks, report the exact Nebula version and setup.

Next steps

The fastest way to judge Nebula is simple: open a real project, run a build, and inspect the files that hurt first.