a fast, scalable, multi-language and extensible build system

Clone this repo:
  1. 32be423 Prepare for the addition of a remote repo contents cache by Fabian Meumertzheim · 6 hours ago main upstream/master
  2. eb1bba0 Move `expand_and_tokenize` from `objc_internal` to `cc_internal`. by ilist · 7 hours ago
  3. 1676373 Refactoring: Eliminate cpp_source from compile_action_templates.bzl and mostly from _create_cc_compile_actions() by pzembrod · 7 hours ago
  4. b653dd9 Allow `rules_cc` to use the `create_compile_action` API. by ilist · 8 hours ago
  5. 9240916 Expose `_cc_internal` via `cc_common.internal_DO_NOT_USE`. by ilist · 8 hours ago

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status