bazel_rules_qt VS Bazel

Compare bazel_rules_qt vs Bazel and see what are their differences.

Bazel

a fast, scalable, multi-language and extensible build system (by bazelbuild)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
bazel_rules_qt Bazel
1 136
44 22,295
- 1.1%
0.0 10.0
about 2 years ago 2 days ago
Starlark Java
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

bazel_rules_qt

Posts with mentions or reviews of bazel_rules_qt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-23.
  • Incremental Builds for Haskell with Bazel
    7 projects | news.ycombinator.com | 23 Jun 2022
    I migrated a mid-size polyglot project from Makefiles to Bazel and C++ was a large component of the project.

    Some obstacles:

    1. Building with QT5 MOC & UI files. There is a great library[0] for it but it has hardcoded paths to the QT binaries and header files assuming a system-wide installation. I had to patch the rule to point to our QT location. Then it worked fine.

    2. There is no rule to build a fully static library[1]. Since we were shipping a static library in our Makefile system, that was somewhat annoying.

    3. We were using system links like `$PROJECT_ROOT/links/GCC/vX.Y.Z/ -> /opt/gcc/...` to point to all the build tools, but these didn't work in Bazel I think because it required absolute paths for any binaries it calls. We ended up putting them in a .bazelrc but we would need a different one for Windows and Linux.

    4. Not good integration with IDEs

    Ultimately we did not keep using Bazel because we were building Python binaries and py_binary was too slow on Windows. And we didn't have enough time to write a PyInstaller rule.

    [0]: https://github.com/justbuchanan/bazel_rules_qt

    [1]: https://github.com/bazelbuild/bazel/issues/1920

Bazel

Posts with mentions or reviews of Bazel. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-18.

What are some alternatives?

When comparing bazel_rules_qt and Bazel you can also consider the following projects:

toolchains_llvm - LLVM toolchain for bazel

Buck - A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.

gcc-toolchain - A fully-hermetic Bazel GCC toolchain for Linux.

nx - Smart Monorepos · Fast CI

nixpkgs - Nix Packages collection & NixOS

meson - The Meson Build System

llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.

Gradle - Adaptable, fast automation for all

rules_python - Bazel Python Rules

ninja - a small build system with a focus on speed

turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]

Apache Maven - Apache Maven core