<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>I have solved it.</p>
<p>@IOhannes your script is pure magic!.</p>
<p>:)<br>
</p>
<pre class="moz-signature" cols="72">Mensaje telepatico asistido por maquinas.</pre>
<div class="moz-cite-prefix">On 1/6/2021 5:45 AM, Lucas Cordiviola
wrote:<br>
</div>
<blockquote type="cite" cite="mid:BN8PR20MB278899F0BA93F53BA1E49F4EA6D00@BN8PR20MB2788.namprd20.prod.outlook.com">
<p>This is a question more for IOhannes and Christof:<br>
<br>
I'm helping with fluid~ for Windows. I got 2 build methods:<br>
<br>
A - download the binaries from fluidsynth for Windows and use
that to build, link and ship dependencies.<br>
it works perfect for w32 and w64 but i'm not sure if it loads
soundfonts compressed in flac/ogg/etc.<br>
<br>
B - download the MSYS2 package of fluidsynth and build with that
and use IOhannes script to ship dependencies.<br>
Works perfect and i think it loads flac/ogg soundfonts but
there's a catchup. The 32bit builds does not load correctly
because is incompatible with Pd's 32bit "libwinpthread-1.dll".<br>
If I place a newer "libwinpthread-1.dll" in Pd/bin it works.<br>
<br>
Don't know what to do.<br>
<br>
May be add a README.pd to tell w32 users to copy the shipped
"libwinpthread-1.dll" to Pd/bin ?</p>
<p><br>
</p>
<p><br>
</p>
<p>--<br>
</p>
<pre class="moz-signature" cols="72">Mensaje telepatico asistido por maquinas.</pre>
<div class="moz-cite-prefix">On 1/5/2021 11:54 PM, Christof Ressi
wrote:<br>
</div>
<blockquote type="cite" cite="mid:d0bbab47-4a4e-004e-3016-b6c6531d14b8@christofressi.com">
<p> </p>
<blockquote type="cite">I see, how can we know and how about
these from fluidsynth? <br>
</blockquote>
<p><a class="moz-txt-link-freetext" href="https://github.com/FluidSynth/fluidsynth/blob/e04cd572cb1ad177519b8e94f27d7be52c074c62/CMakeLists.txt#L62" moz-do-not-send="true">https://github.com/FluidSynth/fluidsynth/blob/e04cd572cb1ad177519b8e94f27d7be52c074c62/CMakeLists.txt#L62</a></p>
<p>The existence of the "BUILD_SHARED_LIBS<span class="pl-s">"
option implies that it *should* be possible to build
fluidsynth as a static library.<br>
</span></p>
<p><span class="pl-s">That being said, if fluidsynth itself
depends on external (shared) libraries, the original problem
persists, because you still would need to link the final
binary with those libraries - or make them static as well.
Etc.<br>
</span></p>
<p><span class="pl-s">---<br>
</span> </p>
<blockquote type="cite">I guess I may have come across a complex
system with over a dozen libs :/ so if I get things straight,
we're better off just keeping it that way?</blockquote>
I think so.<br>
<p>Christof<br>
</p>
<div class="moz-cite-prefix">On 06.01.2021 03:39, Alexandre
Torres Porres wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAEAsFmijt=b8yOEQAV3hmh6jiKKB0KbxiWsxiJTU81djW4v70w@mail.gmail.com">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Em ter., 5 de jan. de
2021 às 20:53, Christof Ressi <<a href="mailto:info@christofressi.com" moz-do-not-send="true">info@christofressi.com</a>>
escreveu:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p> </p>
<blockquote type="cite">I still wonder if there's an
easy way to just incorporate all of these libs
inside the external binary.</blockquote>
Do you mean static linking? </div>
</blockquote>
<div><br>
</div>
<div>guess so :) </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>Depends on the dependencies. Some are available as
a static library and others are not.<br>
</div>
</blockquote>
<div><br>
</div>
<div>I see, how can we know and how about these from
fluidsynth? </div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p>Personally, I strongly prefer static linking for
plugins (like Pd externals). </p>
</div>
</blockquote>
<div>seems best for me too!</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p>The downside is that you're responsible for
providing the correct linker flags, since a static
library is just an archive of object files. For
complex dependencies, you're better off with linking
dynamically and shipping them along side your
library.<br>
</p>
</div>
</blockquote>
<div>I guess I may have come across a complex system with
over a dozen libs :/ so if I get things straight, we're
better off just keeping it that way?</div>
<div><br>
</div>
<div>cheers</div>
</div>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated" href="mailto:Pd-list@lists.iem.at" moz-do-not-send="true">Pd-list@lists.iem.at</a> mailing list
UNSUBSCRIBE and account-management -> <a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-list" moz-do-not-send="true">https://lists.puredata.info/listinfo/pd-list</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list
UNSUBSCRIBE and account-management -> <a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-list">https://lists.puredata.info/listinfo/pd-list</a>
</pre>
</blockquote>
</body>
</html>