# Update jll library

**URL:** <https://discourse.julialang.org/t/update-jll-library/122202>\
**Category:** General Usage\
**Created:** [November 3, 2024, 6:00pm UTC](https://discourse.julialang.org/t/update-jll-library/122202 "2024-11-03T18:00:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheLateKronos](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/thelatekronos/32/12824_2.png) [@TheLateKronos](https://discourse.julialang.org/u/TheLateKronos)\
**Post date:** [November 3, 2024, 6:00pm UTC](https://discourse.julialang.org/t/update-jll-library/122202/1 "2024-11-03T18:00:08Z")

</div>

The [DuckDB\_jll](https://github.com/JuliaBinaryWrappers/DuckDB_jll.jl) library is at 1.1.0:

 ![image](https://global.discourse-cdn.com/julialang/original/3X/f/2/f25b96c78252f02ff50658ebf385a20bd9e4622e.png)

This library seems to be the reason for a failing precompilation of DuckDB.jl on windows, as reported in [this issue](https://github.com/duckdb/duckdb/issues/13911). The last comment in that issue suggest the following fix:

> If the 1.1.1 C/C++ windows library is downloaded from the DuckDB website and an environment variable JULIA\_DUCKDB\_LIBRARY is set to point at duckdb.dll within it, then the latest version will successfully compile in Julia on windows.

So I was just wondering: What is the process of updating an autogenerated jll wrapper to the latest version? Because that might fix the precompilation-on-windows issue for DuckDB.

---

<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:** [November 3, 2024, 10:33pm UTC](https://discourse.julialang.org/t/update-jll-library/122202/2 "2024-11-03T22:33:08Z")

</div>

Open a PR like [[DuckDB] Bump to v1.0.0 by Mytherin · Pull Request #8833 · JuliaPackaging/Yggdrasil · GitHub](https://github.com/JuliaPackaging/Yggdrasil/pull/8833) which updates the version number and the commit hash of the file `D/DuckDB/build_tarballs.jl`.

---

<div class="post-metadata">

**Author:** ![TheLateKronos](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/thelatekronos/32/12824_2.png) [@TheLateKronos](https://discourse.julialang.org/u/TheLateKronos)\
**Post date:** [November 4, 2024, 6:44am UTC](https://discourse.julialang.org/t/update-jll-library/122202/3 "2024-11-04T06:44:29Z")

</div>

Awesome, that was so simple. For future reference, one has to update both the version number and the commit hash. Here is how to find them:

### 1) Click the release that you want to update to

 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/0/2031671da42275ba39ce4d545a6f040c57ad810f.png)

### 2) Click the final commit in the release

 ![image](https://global.discourse-cdn.com/julialang/original/3X/3/a/3a91d0de44f96718aa2d0d62b571ae131a8347a4.png)

### 3) Copy the commit hash from the URL

 ![image](https://global.discourse-cdn.com/julialang/original/3X/c/0/c01e20d5079afd489049bbd5304df6c1af17cba6.png)

And the version that you should tag is visible in all three previous screenshots, so take your pick 🤷