bazel_rules_qt VS llvm-project

Compare bazel_rules_qt vs llvm-project and see what are their differences.


The LLVM Project is a collection of modular and reusable compiler and toolchain technologies. (by llvm)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
bazel_rules_qt llvm-project
1 349
44 25,451
- 3.6%
0.0 10.0
about 2 years ago 3 days ago
Starlark C++
Apache License 2.0 GNU General Public License v3.0 or later
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.


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 | | 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.




Posts with mentions or reviews of llvm-project. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-21.
  • Ask HN: Which books/resources to understand modern Assembler?
    6 projects | | 21 Apr 2024
    'Computer Architeture: A Quantitative Apporach" and/or more specific design types (mips, arm, etc) can be found under the Morgan Kaufmann Series in Computer Architeture and Design.

    "Getting Started with LLVM Core Libraries: Get to Grips With Llvm Essentials and Use the Core Libraries to Build Advanced Tools "

    "The Architecture of Open Source Applications (Volume 1) : LLVM"

    "Tourist Guide to LLVM source code" :

    llvm home page :

    llvm tutorial :

    llvm reference :

    learn by examples : C source code to 'llvm' bitcode :

  • Flang-new: How to force arrays to be allocated on the heap?
    1 project | | 14 Apr 2024

  • The LLVM Compiler Infrastructure
    1 project | | 9 Apr 2024
  • Programming from Top to Bottom - Parsing
    2 projects | | 18 Mar 2024
    You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.
  • Look ma, I wrote a new JIT compiler for PostgreSQL
    1 project | | 18 Mar 2024
    > There is one way to make the LLVM JIT compiler more usable, but I fear it’s going to take years to be implemented: being able to cache and reuse compiled queries.

    Actually, it's implemented in LLVM for years :)

  • C++ Safety, in Context
    8 projects | | 12 Mar 2024
    > It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.

    Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.

    Case in point, this was fixed in both major C++ libraries:

    So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?

  • Clang accepts MSVC arguments and targets Windows if its binary is named clang-cl
    2 projects | | 2 Mar 2024
    For everyone else looking for the magic in this almost 7k lines monster, look at line 6610 [1].


  • Rewrite the VP9 codec library in Rust
    5 projects | | 28 Feb 2024
    Through value tracking. It's actually LLVM that does this, GCC probably does it as well, so in theory explicit bounds checks in regular C code would also be removed by the compiler.

    How it works exactly I don't know, and apparently it's so complex that it requires over 9000 lines of C++ to express:

  • Fortran 2023
    1 project | | 22 Feb 2024
  • MiniScript Ports
    10 projects | | 7 Feb 2024
    • Go • Rust • Lua • pure C (sans C++) • 6502 assembly • WebAssembly • compiler backends, like LLVM or Cranelift

What are some alternatives?

When comparing bazel_rules_qt and llvm-project you can also consider the following projects:

toolchains_llvm - LLVM toolchain for bazel

zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.

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

Lark - Lark is a parsing toolkit for Python, built with a focus on ergonomics, performance and modularity.

nixpkgs - Nix Packages collection & NixOS


rules_python - Bazel Python Rules

SDL - Simple Directmedia Layer

cosmopolitan - build-once run-anywhere c library

windmill - Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.

STL - MSVC's implementation of the C++ Standard Library.

Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀