# \`BinaryBuilder.jl\` steps after successful (manual) build

**URL:** <https://discourse.julialang.org/t/binarybuilder-jl-steps-after-successful-manual-build/134647>\
**Category:** Tooling\
**Tags:** binarybuilder\
**Created:** [December 19, 2025, 5:56pm UTC](https://discourse.julialang.org/t/binarybuilder-jl-steps-after-successful-manual-build/134647 "2025-12-19T17:56:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgeoga](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cgeoga/32/216186_2.png) [@cgeoga](https://discourse.julialang.org/u/cgeoga)\
**Post date:** [December 19, 2025, 5:56pm UTC](https://discourse.julialang.org/t/binarybuilder-jl-steps-after-successful-manual-build/134647/1 "2025-12-19T17:56:59Z")

</div>

Hello,

I have a piece of code that is in Rust that I want to make a dep of a Julia package. I have produced a `build_tarballs.jl` for the library that runs successfully and have checked that the resulting `jll` library works successfully locally on my machine. I couldn’t use the wizard because of some known errors around compiling Rust libraries, though, and I’m not confident in my understanding of the docs about what to do now.

If I’m reading [these docs](https://docs.binarybuilder.org/stable/reference/#Command-Line) correctly, it looks like I should just

```julia-auto
julia +1.7 --project build_tarballs.jl --deploy

```

which will then create a repository `https://github.com/JuliaBinaryWrappers/{mylib}_jll`. After doing that, though, should I also be making a PR to `Yggrdasil` with the `build_tarballs.jl` file? The `Contributing.md` has notes on commit messages, for example, which makes me think that I should be doing that. But considering how manual PRs to the `General` registry are not common, I figure I would ask before doing that and potentially making some computer cores that do automatic building or something spin up for no reason.

Please excuse me if I’ve missed some relevant documentation. And also: seriously incredible how this all works. It is very intimidating to me to try and do this, but between the documentation and discussion on forums and issues and stuff within a few hours of tinkering I got something up and running. Pretty amazing.

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [December 19, 2025, 6:20pm UTC](https://discourse.julialang.org/t/binarybuilder-jl-steps-after-successful-manual-build/134647/2 "2025-12-19T18:20:45Z")

</div>

> [@cgeoga](#):
>
> After doing that, though, should I also be making a PR to `Yggrdasil` with the `build_tarballs.jl` file?

It’s the opposite! By creating a pull request for a new build script in Yggy, CI will try building for all platforms. And then upon green checks and a merge, it auto-generates all things for you — both the repo in the `JuliaBinaryWrappers` org and the registration.

---

<div class="post-metadata">

**Author:** ![cgeoga](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cgeoga/32/216186_2.png) [@cgeoga](https://discourse.julialang.org/u/cgeoga)\
**Post date:** [December 19, 2025, 8:37pm UTC](https://discourse.julialang.org/t/binarybuilder-jl-steps-after-successful-manual-build/134647/3 "2025-12-19T20:37:18Z")

</div>

Ah, wonderful, that makes sense! Thanks so much.
