bazel_rules_qt VS nixpkgs

Compare bazel_rules_qt vs nixpkgs and see what are their differences.

bazel_rules_qt

Bazel rules for Qt5 (by justbuchanan)

nixpkgs

Nix Packages collection (by NixOS)
Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
bazel_rules_qt nixpkgs
1 607
39 10,109
- 2.4%
2.7 10.0
6 months ago 5 days ago
Starlark Nix
Apache License 2.0 MIT License
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

nixpkgs

Posts with mentions or reviews of nixpkgs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-12.

What are some alternatives?

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

asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more

Home Manager using Nix - Manage a user environment using Nix [[email protected]]

git-lfs - Git extension for versioning large files

easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications

daedalus - The open source cryptocurrency wallet for ada, built to grow with the community

youtube-dl-gui - A cross-platform GUI for youtube-dl made in Electron and node.js

nixos - My NixOS Configurations

devshell - Per project developer environments

nonguix

HomeBrew - 🍺 The missing package manager for macOS (or Linux)

Emu68 - M68K emulation for AArch64/AArch32

spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.