# \[ANN\] JuliaLibWrapping.jl: bringing Julia libraries to C and Python users

**URL:** <https://discourse.julialang.org/t/ann-julialibwrapping-jl-bringing-julia-libraries-to-c-and-python-users/139150>\
**Category:** Package Announcements\
**Tags:** python, static-compilation\
**Created:** [September 1, 2026, 11:36pm UTC](https://discourse.julialang.org/t/ann-julialibwrapping-jl-bringing-julia-libraries-to-c-and-python-users/139150 "2026-09-01T23:36:24Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [September 2, 2026, 7:08pm UTC](https://discourse.julialang.org/t/ann-julialibwrapping-jl-bringing-julia-libraries-to-c-and-python-users/139150/12 "2026-09-02T19:08:37Z")

</div>

> **[Bundling for distribution - Building and distribution · JuliaLibWrapping.jl](https://juliainterop.github.io/JuliaLibWrapping.jl/dev/building/#Bundling-for-distribution)**
>
> standard\_build handles the conventional package layout. Use build\_library when you need to select targets, paths, bundling, or other compilation options explicitly. | Documentation for JuliaLibWrapping.jl.

> Test a distribution with `pip install` in a clean virtual environment on such a machine.

I’m not involved with the project just posting what seems relevant above and:

> Pass `privatize = false` only when that isolation is knowingly unnecessary.
> 
> Only the Julia runtime libraries are privatized. BLAS, Fortran, and unwind libraries may still be shared. Bundles produced by different Julia versions have not been established as mutually compatible. This behavior has been measured on Linux; macOS and Windows follow different loader rules and have not been tested equivalently.

> [@asinghvi17](#):
>
> I assume we’d have to lock the versions of libraries Julia needs, like openssl, openblas, etc

I suppose this will not be a problem, no more than for `JuliaCall` / PythonCall.jl (not sure about for R for the future or or what currently happens when it’s used with RCall.jl, hopefully also just works…) that would have had the exact same version problems. For at least OpenBLAS (maybe OpenSSL, as I recall there was such a problem, I think already solved).

[The rest of my answer is in edit history (my whole post was flagged, I guess for the AI answer in the end, so I deleted it, I still think that part was correct).]

---

_[View the full topic](https://discourse.julialang.org/t/ann-julialibwrapping-jl-bringing-julia-libraries-to-c-and-python-users/139150)._