<div dir="ltr">
<div style="color:rgb(212,212,212);background-color:rgb(30,30,30);font-family:Consolas,"Courier New",monospace;font-weight:normal;font-size:14px;line-height:19px;white-space:pre"><div><span style="color:rgb(212,212,212)">Hello,</span></div><br><div><span style="color:rgb(212,212,212)">Please find attached a patch to enable using S7 across DLLs on Microsoft Windows.</span></div><br><div><span style="color:rgb(212,212,212)">In Windows, if there are functions in a Library or EXE that are intended to be used in a different Library or EXE, then those functions must be "exported". </span></div><div><span style="color:rgb(212,212,212)">To export, functions are marked with the "__declspec(dllexport)" annotation, in the implementation library. </span></div><div><span style="color:rgb(212,212,212)">That will cause the symbols to be included in the generated ".lib" file. </span></div><div><span style="color:rgb(212,212,212)">This will enable the importing library to find the symbols during the linking step.</span></div><br><div><span style="color:rgb(212,212,212)">The patch adds an export macro to all the S7 api functions. By default, the export annotation has no effect; the export behavior is opt-in.</span></div><div><span style="color:rgb(212,212,212)">The opt-in is done by defining the symbol 'S7_EXPORT_LIB' in the implementation library.</span></div><br><div><span style="color:rgb(212,212,212)">I wrote this patch myself, and I hereby release it into the public domain.</span></div><br><div><span style="color:rgb(212,212,212)">Thanks,</span></div><div><span style="color:rgb(212,212,212)">Vlad F</span></div></div>
</div>