<html>
<body>
Binary or source? <br><br>
Source is somewhat complex, as using the generated intersci code requires
(for version 5.3) linking against <br><br>
libf2c.lib;intersci.lib;libscilab.lib;output_stream.lib;blasplus.lib;<br>
<br>
as well as <br><br>
elementary_functions.lib;elementary_functions_f.lib<br><br>
the latter two are not actually part of the scilab distribution, so I
generated them myself by creating def files using DUMPBIN.exe (from the
DLL files) and creating the lib files using lib.exe (from the def files).
If not linked against elementary_functions.lib,
<font face="Consolas" size=2>int2db_ </font>is missing. If not linked
against elementary)functions_f.lib,
<font face="Consolas" size=2>entier_</font> is missing.<br><br>
A disadvantage of the whole DLL approach is that I need to redo this at
each major scilab release (as the import libraries change from version to
version). Version 5.3 was the first one for which I had to generate
import libs myself, for previous versions all required import libs were
in the bin folder. Version 5.2 for example required linking against
<br><br>
libf2c.lib;intersci.lib;libscilab.lib;output_stream.lib;blasplus.lib;<br>
<br>
but not against elementary_functions.lib;elementary_functions_f.lib.
Version 5.1 required linking against <br><br>
libf2c.lib;intersci.lib;libscilab.lib;scioutput_stream.lib;blasplus.lib;<br>
<br>
So personally I am looking forward to a more generic method like
SWIG.<br><br>
Best wishes, <br><br>
Jasper<br><br>
At 15:23 4/26/2011, Allan CORNET wrote:<br>
<blockquote type=cite class=cite cite="">Hi,<br>
<br>
Can you attach or send to me a small example ?<br>
<br>
Thanks <br>
<br>
Allan<br>
<br>
<b>De :</b> jasper van baten
[<a href="mailto:jasper@amsterchem.com" eudora="autourl">
mailto:jasper@amsterchem.com</a>] <br>
<b>Envoyé :</b> mardi 26 avril 2011 13:53<br>
<b>À :</b> users@lists.scilab.org; users@lists.scilab.org<br>
<b>Objet :</b> Re: [scilab-Users] SWIG?<br>
<br>
Hello, <br><br>
So I gather from that that intersci is at the moment still the way to go
in case you want things to work out-of-the-box.<br><br>
Are there known problems with the x64 implementation of intersci? I get,
for a DLL that is compiled x64 and linked against the x64 scilab import
libraries, the following message after addinter:<br><br>
Shared archive loaded.<br>
Link done.<br>
sluofuncs_ is not an entry point.<br>
Shared archive loaded.<br>
Link done.<br>
sluofuncs is not an entry point.<br>
addinter([dllName],'sluofuncs',sluofuncsfuns);<br>
!--error 999 <br>
addinter: An error occurred: The specified module could not be found.
<br><br>
The module can most certainly be found, and gets loaded as well. It
complains about the "sluofuncs_" entrypoint not being there,
but it is there (can easily verify that, e.g. with the dependency
viewer). The entrypoints are all generated with intersci-n.exe and
f2c.exe and exactly the same procedure works fine for the x86
version.<br><br>
Thank you, <br><br>
Best wishes, <br><br>
Jasper.<br><br>
At 09:16 4/26/2011, Vincent COUVERT wrote:<br><br>
Hi,<br><br>
The SWIG implementation is not yet released but is available in a
dedicated branch [1]. We are still working on it and hope this will be
included in a future SWIG official release.<br><br>
Best Regards.<br><br>
[1]
<a href="http://swig.svn.sourceforge.net/viewvc/swig/branches/gsoc2009-sploving/">
http://swig.svn.sourceforge.net/viewvc/swig/branches/gsoc2009-sploving/</a>
<br><br>
<br><br>
<br>
Le 25/04/11 16:15, jasper van baten a écrit :<br><br>
Hello All,<br><br>
I read in the 5.3.1 documentation that intersci is obsolete, and is to be
replaced by SWIG. Is this SWIG implementation ready to use at this point?
Is there any documentation?<br><br>
Best wishes,<br><br>
Jasper.</blockquote></body>
</html>