<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 318: Different macOS libwrapper extensions</title><link href="https://sourceforge.net/p/wrapper/bugs/318/" rel="alternate"/><link href="https://sourceforge.net/p/wrapper/bugs/318/feed.atom" rel="self"/><id>https://sourceforge.net/p/wrapper/bugs/318/</id><updated>2022-01-10T12:41:54.911000Z</updated><subtitle>Recent changes to 318: Different macOS libwrapper extensions</subtitle><entry><title>#318 Different macOS libwrapper extensions</title><link href="https://sourceforge.net/p/wrapper/bugs/318/?limit=25#66c4" rel="alternate"/><published>2022-01-10T12:41:54.911000Z</published><updated>2022-01-10T12:41:54.911000Z</updated><author><name>Leif Mortenson</name><uri>https://sourceforge.net/u/mortenson/</uri></author><id>https://sourceforge.netef455e16814e824b3d16cafa62a6ab2f2503e1b4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The file extensions are actually decided by the JVM.  Those are the extensions that Java is expecting when loading JNI native libraries.  I don't think there is anything we can do about it.&lt;br/&gt;
Other UNIX platforms also have other extensions.&lt;br/&gt;
I agree that it would be nice to be able to keep them all the same.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;br/&gt;
Leif&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Different macOS libwrapper extensions</title><link href="https://sourceforge.net/p/wrapper/bugs/318/" rel="alternate"/><published>2022-01-10T12:02:31.214000Z</published><updated>2022-01-10T12:02:31.214000Z</updated><author><name>Adrian Ho</name><uri>https://sourceforge.net/u/gromgit/</uri></author><id>https://sourceforge.net1926e2a1d3762b9e5350d913341ff6a522d4a66b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi! I help out with the Homebrew project, and we just noticed the following chunk in &lt;code&gt;build.xml&lt;/code&gt;:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&amp;lt;release-delta-extract-platform osname="macosx"  osarch="universal" bits="32" wrapperbinhead="wrapper" wrapperbintail=""     wrapperlibhead="libwrapper" wrapperlibtail=".jnilib" archivetype="tar.gz"/&amp;gt;
&amp;lt;release-delta-extract-platform osname="macosx"  osarch="universal" bits="64" wrapperbinhead="wrapper" wrapperbintail=""     wrapperlibhead="libwrapper" wrapperlibtail=".jnilib" archivetype="tar.gz"/&amp;gt;
&amp;lt;release-delta-extract-platform osname="macosx"  osarch="arm"       bits="64" wrapperbinhead="wrapper" wrapperbintail=""     wrapperlibhead="libwrapper" wrapperlibtail=".dylib"  archivetype="tar.gz"/&amp;gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;and similar differentiation in the macOS Makefiles.&lt;/p&gt;
&lt;p&gt;Is there a reason why the macOS wrapper library has a &lt;code&gt;.jnilib&lt;/code&gt; extension on Intel, but &lt;code&gt;.dylib&lt;/code&gt; on Apple Silicon? Will this be unified to &lt;code&gt;.dylib&lt;/code&gt; in a future release?&lt;/p&gt;
&lt;p&gt;Thanks much!&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>