# JuliaCon 2025 Hackathon Ideas!

**URL:** <https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956>\
**Category:** 2025\
**Tags:** juliacon, hackathon\
**Created:** [July 22, 2025, 6:55pm UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956 "2025-07-22T18:55:57Z")\
**Posts on this page:** 5\
**Page:** 2

<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:** [July 27, 2025, 2:35am UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956/21 "2025-07-27T02:35:31Z")

</div>

For C code why don’t you use Clang.jl instead?

---

<div class="post-metadata">

**Author:** ![asinghvi17](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/asinghvi17/32/8272_2.png) [@asinghvi17](https://discourse.julialang.org/u/asinghvi17)\
**Post date:** [July 27, 2025, 2:42am UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956/22 "2025-07-27T02:42:23Z")

</div>

It’s a C++ library unfortunately with no C API, that has to get generated somehow though.

---

<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:** [July 27, 2025, 2:48am UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956/23 "2025-07-27T02:48:39Z")

</div>

Ah, I misunderstood the part about C API in your previous message.

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [July 27, 2025, 3:32am UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956/24 "2025-07-27T03:32:52Z")

</div>

> [@jling](#):
>
> Getting `juliac.jl` to emit header files together for better integration with other ecosystems that want to use Julia compiled `.so` as backend.

[PoC by @ChrisRackauckas](https://gist.github.com/ChrisRackauckas/181569d8c3ec892b29dda48359abf865)

> [@jling](#):
>
> Fix lowering of `@atomic` for floats on shared memory for Metal backend

> <https://github.com/JuliaConcurrent/Atomix.jl/pull/60>
>
> fix #59
> 
> depends on https://github.com/JuliaGPU/Metal.jl/pull/636

---

<div class="post-metadata">

**Author:** ![ohmsweetohm1](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ohmsweetohm1/32/49126_2.png) [@ohmsweetohm1](https://discourse.julialang.org/u/ohmsweetohm1)\
**Post date:** [July 31, 2025, 9:45am UTC](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956/25 "2025-07-31T09:45:12Z")

</div>

Handle (warn) package relocatability issues. [Could the package compiler check for relocatabiliy? · Issue #1050 · JuliaLang/PackageCompiler.jl · GitHub](https://github.com/JuliaLang/PackageCompiler.jl/issues/1050)

Not a real solution to the problem but at least a user that creates an app would know.

[Previous page](https://discourse.julialang.org/t/juliacon-2025-hackathon-ideas/130956.md?page=1)