[scilab-Users] CallScilab under Windows

Allan CORNET allan.cornet at scilab.org
Fri Jan 21 19:49:39 CET 2011


Hi,

See example in 

SCI/modules/call_scilab/examples/call_scilab/c/visual_studio

Or 
http://gitweb.scilab.org/?p=scilab.git;a=tree;f=scilab/modules/call_scilab/e
xamples/call_scilab/c/visual_studio;h=1eeccb37d0fa951f44c6482728547514e6986c
54;hb=55d87ead63cf8017d4692f28e8f7a59b99607f09


Allan

-----Message d'origine-----
De : Mike Page [mailto:Mike at Page-One.Waitrose.com] 
Envoyé : vendredi 21 janvier 2011 19:45
À : users at lists.scilab.org
Objet : [scilab-Users] CallScilab under Windows

Hi,

Has anyone managed to get CallScilab to work under Windows?  The information
on the web page is mainly for Linux and is hard to convert.

I am using a pre-compiled version of Scilab 5.3.0 under Windows XP and have
built the example C source code (from
http://www.scilab.org/product/man/call_scilab.html) with Visual C++ Express
2010.

I got the include files from the directories:
C:\Program Files\Scilab-5.3.0\modules\call_scilab\includes
C:\Program Files\Scilab-5.3.0\modules\api_scilab\includes
C:\Program Files\Scilab-5.3.0\modules\core\includes

and the lib files from:

C:\Program Files\Scilab-5.3.0\bin\api_scilab.lib and call_scilab.lib

I have C:\Program Files\Scilab-5.3.0\bin in the Path so that the DLLs can be
located at run time.

The example builds OK, but there are two warnings:

1. The example includes stack_c.h, which is deprecated.  I changed it to
api_scilab.h instead.

2. The third parameter of StartScilab is given as NULL, but the prototype
has this as an int (although the documentation says int*).  I changed it to
0 which shouldn't make any functional difference.

That got an error-free and warning-free build.

When I run the code, the call to StartScilab generates an error:

"Impossible to read <path to my executable>\etc\jvm_options.xml"

Should there be a path or environment variable setting for this?  I have an
environment variable SCI set to C:\Program Files\Scilab-5.3.0.

I copied the directory C:\Program Files\Scilab-5.3.0\etc to <path to my
executable>\etc so that I would have a default jvm_options file and the
error changes to:

"Scilab cannot create Scilab Java Main-Cass (we have not been able to find
the main Scilab class. Check if the Scilab and thirdparty packages are
available)."

Any suggestions as to where I go from here.  It looks like I am missing some
step in the configuration.

Thanks,
Mike.





More information about the users mailing list