Introduction

rebaze analyzes your CMake or Gradle project and generates Bazel build files automatically.

rebaze migrate /path/to/project

Output:

• MODULE.bazel — Dependencies and module definition
• BUILD.bazel — Build targets for your code
• .bazelversion — Pins Bazel 9.x
• .bazelrc — Sensible defaults

What rebaze does

1. Analyze

Detects your build system and parses build files

2. Transform

Maps dependencies to Bazel targets

3. Generate

Writes MODULE.bazel and BUILD.bazel files

4. Validate

Verifies the migration builds successfully

Why migrate to Bazel?

If you’re considering Bazel, you probably already know why. For the record:

Benefit	What it means
Fast incremental builds	Only rebuilds what changed
Hermetic builds	Same inputs → same outputs, always
Remote caching	Share build artifacts across your team
Remote execution	Distribute builds across machines
Multi-language	C++, Java, Go, Python in one repo

Why use rebaze?

Manual migration is tedious:

1. Learning Starlark syntax
2. Writing BUILD files for every directory
3. Mapping every dependency to Bazel targets
4. Handling platform-specific configurations

rebaze handles all of this. You focus on your code.

Supported build systems

Source	Status	Notes
CMake	Supported	Full parser + cmake-file-api
Gradle	Supported	Groovy and Kotlin DSL
Maven	Planned	Detection only

Early development

rebaze is under active development. It works well for standard project structures but may need manual adjustments for complex builds.

Limitations

Be aware of current limitations:

• CMake: Generator expressions partially supported
• Gradle: Android projects not yet supported
• General: Custom build logic may need manual migration

Next steps

Ready? Pick your path:

Quick Start Migrate your first project in 60 seconds

Installation Install via Homebrew or build from source

CMake Tutorial Detailed CMake migration walkthrough

Gradle Tutorial Detailed Gradle migration walkthrough