Binary Dependency Builder for Julia (by JuliaPackaging)

BinaryBuilder.jl Alternatives

Similar projects and alternatives to BinaryBuilder.jl

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

BinaryBuilder.jl reviews and mentions

Posts with mentions or reviews of BinaryBuilder.jl. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-30.
  • Is Julia suitable today as a scripting language?
    6 projects | /r/Julia | 30 Jan 2023
    There are some efforts and the startup times are getting better with every release and there's BinaryBuilder.jl.
  • Because cross-compiling binaries for Windows is easier than building natively
    15 projects | | 18 Jun 2022
    There is the Julia package which creates an environment that fakes being another, but with the correct compilers and SDKs . It's used to build all the binary dependencies
  • Discussion Thread
    2 projects | /r/neoliberal | 16 Apr 2022 You can do it manually obviously, but this is easier.
  • PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
    18 projects | | 26 Nov 2021
    > The main pain point is probably the lack of standard, multi-environment packaging solutions for natively compiled code.

    Are you talking about something like BinaryBuilder.jl[1], which provides native binaries as julia-callable wrappers?



  • What to do about GPU packages on PyPI?
    7 projects | | 20 May 2021
    Julia did that for binary dependencies for a few years, with adapters for several linux platforms, homebrew, and for cross-compiled RPMs for Windows. It worked, to a degree -- less well on Windows -- but the combinatorial complexity led to many hiccups and significant maintenance effort. Each Julia package had to account for the peculiarities of each dependency across a range of dependency versions and packaging practices (linkage policies, bundling policies, naming variations, distro versions) -- and this is easier in Julia than in (C)Python because shared libraries are accessed via locally-JIT'd FFI, so there is no need to eg compile extensions for 4 different CPython ABIs (Julia also has syntactic macros which can be helpful here).

    To provide a better experience for both package authors and users, as well as reducing the maintenance burden, the community has developed and migrated to a unified system called BinaryBuilder ( over the past 2-3 years. BinaryBuilder allows targeting all supported platforms with a single build script and also "audits" build products for common compatibility and linkage snafus (similar to some of the conda-build tooling and auditwheel). There was a nice talk at AlpineConf recently ( covering some of this history and detailing BinaryBuilder, although I'm not sure how to link into the video.

    All that to say: it can work to an extent, but it has been tried various times before. The fact that conda and manylinux don't use system packages was not borne out of inexperience, either. The idea of "make binaries a distro packager's problem" sounds like a simplifying step, but that doesn't necessarily work out.

  • A note from our sponsor - SonarQube | 25 Sep 2023
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →


Basic BinaryBuilder.jl repo stats
5 days ago
Updating dependencies is time-consuming.
Solutions like Dependabot or Renovate update but don't merge dependencies. You need to do it manually while it could be fully automated! Add a Merge Queue to your workflow and stop caring about PR management & merging. Try Mergify for free.