<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Native on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/native/</link>
    <description>Recent content in Native on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/native/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JNA vs JNR vs Project Panama in 2026: Calling C from Java Without JNI Glue</title>
      <link>https://www.pistack.xyz/posts/2026-11-04-jna-vs-jnr-vs-project-panama-java-native-interop/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-04-jna-vs-jnr-vs-project-panama-java-native-interop/</guid>
      <description>&lt;p&gt;Every JVM project that touches native code hits the same wall. You need one function from a C library — &lt;code&gt;getpid&lt;/code&gt;, a hardware SDK, a codec, a GPU driver — and the official answer is JNI: write a C header, write a C implementation, compile it per platform, ship a &lt;code&gt;.so&lt;/code&gt;/&lt;code&gt;.dll&lt;/code&gt;/&lt;code&gt;.dylib&lt;/code&gt; for every OS and architecture, then debug segmentation faults in a language your team does not write.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
