# Understanding build products

**URL:** <https://discourse.julialang.org/t/understanding-build-products/128278>\
**Category:** General Usage\
**Tags:** binarybuilder\
**Created:** [April 21, 2025, 11:34pm UTC](https://discourse.julialang.org/t/understanding-build-products/128278 "2025-04-21T23:34:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![luke-kiernan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/luke-kiernan/32/214309_2.png) [@luke-kiernan](https://discourse.julialang.org/u/luke-kiernan)\
**Post date:** [April 21, 2025, 11:34pm UTC](https://discourse.julialang.org/t/understanding-build-products/128278/1 "2025-04-21T23:34:25Z")

</div>

There’s a windows-specific [issue](https://github.com/JuliaSmoothOptimizers/MUMPS.jl/issues/110) with [`MUMPS_jll`](https://github.com/JuliaPackaging/Yggdrasil/tree/master/M/MUMPS/MUMPS%405) on Yggdrasil, so I’m trying to troubleshoot. As I understand things, I need to:

1. Tweak the build script.
2. Compile for the target system: on a Mac/Linux system, tell `BinaryBuilder.jl` to run the build script.
3. Move the resulting product to a windows machine.
4. Build the product on the host system: run the product, which creates a `MUMPS_jll`.
5. Tell `MUMPS.jll` to use that `MUMPS_jll` (instead of the Yggdrasil one) and see if the problem is resolved.

After carefully reading the `BinaryBuilder.jl` docs, I can do steps 1 and 2:

```julia
juliaup add 1.7 # BinaryBuilder.jl requires Julia 1.7
git clone https://github.com/JuliaPackaging/Yggdrasil.git
cd Yggrasil/M/MUMPS/MUMPS@5/
# package setup. (I did this in REPL, so may not be quite right)
julia +1.7 -e "using Pkg; Pkg.activate(\".\"); Pkg.instantiate(); Pkg.add(\"BinaryBuilder\");"
open /Applications/Docker.app # launch Docker.
# build for target.
julia +1.7 build_tarballs.jl --project --debug --verbose x86_64-w64-mingw32

```

That yields some useful diagnostic stuff. Also, 5 is covered in the docs [here](https://docs.binarybuilder.org/stable/building/#Building-and-testing-JLL-packages-locally). What about steps 3 and 4? I can see a new `MUMPS.v5.7.3.x86_64-w64-mingw32.tar.gz` file under build products…

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [April 22, 2025, 6:33am UTC](https://discourse.julialang.org/t/understanding-build-products/128278/2 "2025-04-22T06:33:39Z")

</div>

You can publish the JLL to a GitHub repo of your choice with `--deploy=username/MUMPS_jll.jl`, see [Reference · BinaryBuilder.jl](https://docs.binarybuilder.org/stable/reference/#Command-Line). If you do that, then you can install the package on another machine by `]add`ing the corresponding URL