bazel_rules_qt

Bazel rules for Qt5 (by justbuchanan)

Bazel_rules_qt Alternatives

Similar projects and alternatives to bazel_rules_qt

  1. nixpkgs

    Nix Packages collection & NixOS

  2. InfluxDB

    InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

    InfluxDB logo
  3. llvm-project

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

  4. Bazel

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

  5. rules_python

    Bazel Python Rules

  6. toolchains_llvm

    LLVM toolchain for bazel

  7. gcc-toolchain

    A fully-hermetic Bazel GCC toolchain for Linux.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better bazel_rules_qt alternative or higher similarity.

bazel_rules_qt discussion

Log in or Post with

bazel_rules_qt reviews and mentions

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

Stats

Basic bazel_rules_qt repo stats
1
48
2.5
6 months ago

justbuchanan/bazel_rules_qt is an open source project licensed under Apache License 2.0 which is an OSI approved license.

The primary programming language of bazel_rules_qt is Starlark.


Sponsored
InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com