Reg :: Integration of Scilab-4.2.1 with C++ from Linux

classic Classic list List threaded Threaded
11 messages Options
Sumit Adhikari Sumit Adhikari
Reply | Threaded
Open this post in threaded view
|

Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Hello,
  Is there any way to integrate scilab-4.2.1 in 64-bit RHEL. I want to use Scilab macros in my C++ Design.
  When I try, I get some library errors!
Regards,
Sumit
sylvestre sylvestre
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Le mardi 25 août 2009 à 11:20 +0530, Sumit Adhikari a écrit :
> Hello,
>   Is there any way to integrate scilab-4.2.1 in 64-bit RHEL.
Yep, it should work but 4.X family is no longer supported.

> I want to use Scilab macros in my C++ Design.
>   When I try, I get some library errors!
What kind of errors ?

Sylvestre

--
-------------------------
Sylvestre Ledru
-------------------------
The Scilab Consortium
Digiteo
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex
France


Sumit Adhikari Sumit Adhikari
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

I am getting errors on all this non-existing objects!

linking
g77: ../../../routines/default/FTables.o: No such file or directory
g77: ../../../routines/default/Ex-colnew.o: No such file or directory
g77: ../../../routines/default/Ex-corr.o: No such file or directory
g77: ../../../routines/default/Ex-feval.o: No such file or directory
g77: ../../../routines/default/Ex-fsolve.o: No such file or directory
g77: ../../../routines/default/Ex-lsqrsolve.o: No such file or directory
g77: ../../../routines/default/Ex-impl.o: No such file or directory
g77: ../../../routines/default/Ex-intg.o: No such file or directory
g77: ../../../routines/default/Ex-int2d.o: No such file or directory
g77: ../../../routines/default/Ex-int3d.o: No such file or directory
g77: ../../../routines/default/Ex-ode-more.o: No such file or directory
g77: ../../../routines/default/Ex-ode.o: No such file or directory
g77: ../../../routines/default/Ex-odedc.o: No such file or directory
g77: ../../../routines/default/Ex-optim.o: No such file or directory
g77: ../../../routines/default/Ex-schur.o: No such file or directory
g77: ../../../routines/default/Ex-fort.o: No such file or directory
g77: ../../../routines/default/Ex-dasrt.o: No such file or directory
g77: ../../../routines/default/Ex-dassl.o: No such file or directory
g77: ../../../routines/default/Ex-fbutn.o: No such file or directory
g77: ../../../routines/default/matusr.o: No such file or directory
g77: ../../../routines/default/matus2.o: No such file or directory
g77: ../../../routines/default/Funtab.o: No such file or directory
g77: ../../../routines/default/msgstxt.o: No such file or directory
g77: ../../../routines/default/scimem.o: No such file or directory
g77: ../../../routines/default/callinterf.o: No such file or directory
g77: ../../../routines/default/mexlib.o: No such file or directory
g77: ../../../libs/libXaw3d.a: No such file or directory
g77: ../../../libs/libXmu.a: No such file or directory
g77: ../../../libs/system.a: No such file or directory
g77: ../../../libs/console.a: No such file or directory
g77: ../../../libs/interf.a: No such file or directory
g77: ../../../libs/system2.a: No such file or directory
g77: ../../../libs/optim.a: No such file or directory
g77: ../../../libs/scicos.a: No such file or directory
g77: ../../../libs/integ.a: No such file or directory
g77: ../../../libs/control.a: No such file or directory
g77: ../../../libs/signal.a: No such file or directory
g77: ../../../libs/poly.a: No such file or directory
g77: ../../../libs/calelm.a: No such file or directory
g77: ../../../libs/lapack.a: No such file or directory
g77: ../../../libs/graphics.a: No such file or directory
g77: ../../../libs/sparse.a: No such file or directory
g77: ../../../libs/metanet.a: No such file or directory
g77: ../../../libs/os_specific.a: No such file or directory
g77: ../../../libs/gd.a: No such file or directory
g77: ../../../libs/intersci.a: No such file or directory
g77: ../../../libs/xsci.a: No such file or directory
g77: ../../../libs/graphics.a: No such file or directory
g77: ../../../libs/menusX.a: No such file or directory
g77: ../../../libs/fileio.a: No such file or directory
g77: ../../../libs/dcd.a: No such file or directory
g77: ../../../libs/rand.a: No such file or directory
g77: ../../../libs/blas.a: No such file or directory
g77: ../../../libs/int.a: No such file or directory
g77: ../../../libs/slicot.a: No such file or directory
g77: ../../../libs/arpack.a: No such file or directory
g77: ../../../libs/wintools.a: No such file or directory
g77: ../../../libs/pvm.a: No such file or directory
g77: ../../../libs/tclsci.a: No such file or directory
g77: /fshy01/uxhyu/sa1/tools/scilab-4.1.2/pvm3/lib/LINUX/libgpvm3.a: No such file or directory
g77: /fshy01/uxhyu/sa1/tools/scilab-4.1.2/pvm3/lib/LINUX/libpvm3.a: No such file or directory
g77: ../../../libs/libXaw3d.a: No such file or directory
g77: ../../../libs/libXmu.a: No such file or directory
make[1]: *** [myprog] Error 1
make[1]: Leaving directory `/fshy01/uxhyu/sa1/tools/scilab-4.1.2/examples/callsci/callsciC++'
make: *** [all] Error 2



On Sat, Sep 12, 2009 at 3:02 AM, Sylvestre Ledru <[hidden email]> wrote:
Le mardi 25 août 2009 à 11:20 +0530, Sumit Adhikari a écrit :
> Hello,
>   Is there any way to integrate scilab-4.2.1 in 64-bit RHEL.
Yep, it should work but 4.X family is no longer supported.

> I want to use Scilab macros in my C++ Design.
>   When I try, I get some library errors!
What kind of errors ?

Sylvestre

--
-------------------------
Sylvestre Ledru
-------------------------
The Scilab Consortium
Digiteo
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex
France


sylvestre sylvestre
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Le lundi 14 septembre 2009 à 12:13 +0530, Sumit Adhikari a écrit :
> I am getting errors on all this non-existing objects!
>
> linking
> g77: ../../../routines/default/FTables.o: No such file or directory
[...]

> g77: ../../../libs/pvm.a: No such file or directory
> g77: ../../../libs/tclsci.a: No such file or directory
> g77: /fshy01/uxhyu/sa1/tools/scilab-4.1.2/pvm3/lib/LINUX/libgpvm3.a:
> No such file or directory
> g77: /fshy01/uxhyu/sa1/tools/scilab-4.1.2/pvm3/lib/LINUX/libpvm3.a: No
> such file or directory
> g77: ../../../libs/libXaw3d.a: No such file or directory
> g77: ../../../libs/libXmu.a: No such file or directory
> make[1]: *** [myprog] Error 1
> make[1]: Leaving directory
> `/fshy01/uxhyu/sa1/tools/scilab-4.1.2/examples/callsci/callsciC++'
> make: *** [all] Error 2
Well, I cannot help you here...
Scilab 5 family has been completed rewrite on the build process and is
now much more appropriate for such operations ... (shared lib, real
build system, etc).

Sylvestre



Sumit Adhikari Sumit Adhikari
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Hmm, I know. But my limitation is that my systemc dosent have proper glibc version and for that It needs to be upgraded. :(
Thanks anyway.
Regards,
Sumit

On Mon, Sep 14, 2009 at 1:13 PM, Sylvestre Ledru <[hidden email]> wrote:
Le lundi 14 septembre 2009 à 12:13 +0530, Sumit Adhikari a écrit :
> I am getting errors on all this non-existing objects!
>
> linking
> g77: ../../../routines/default/FTables.o: No such file or directory
[...]
> g77: ../../../libs/pvm.a: No such file or directory
> g77: ../../../libs/tclsci.a: No such file or directory
> g77: /fshy01/uxhyu/sa1/tools/scilab-4.1.2/pvm3/lib/LINUX/libgpvm3.a:
> No such file or directory
> g77: /fshy01/uxhyu/sa1/tools/scilab-4.1.2/pvm3/lib/LINUX/libpvm3.a: No
> such file or directory
> g77: ../../../libs/libXaw3d.a: No such file or directory
> g77: ../../../libs/libXmu.a: No such file or directory
> make[1]: *** [myprog] Error 1
> make[1]: Leaving directory
> `/fshy01/uxhyu/sa1/tools/scilab-4.1.2/examples/callsci/callsciC++'
> make: *** [all] Error 2
Well, I cannot help you here...
Scilab 5 family has been completed rewrite on the build process and is
now much more appropriate for such operations ... (shared lib, real
build system, etc).

Sylvestre



sylvestre sylvestre
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Le lundi 14 septembre 2009 à 13:24 +0530, Sumit Adhikari a écrit :
> Hmm, I know. But my limitation is that my systemc dosent have proper
> glibc version and for that It needs to be upgraded. :(
This problem has been fixed in the current nightly build of the 5.1.X
family.

Sylvestre



Sumit Adhikari Sumit Adhikari
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Got it now. This time it is very organized. Thanks for this info. By the way, do you have any document for so many APIs
Regards,
Sumit

On Mon, Sep 14, 2009 at 1:26 PM, Sylvestre Ledru <[hidden email]> wrote:
Le lundi 14 septembre 2009 à 13:24 +0530, Sumit Adhikari a écrit :
> Hmm, I know. But my limitation is that my systemc dosent have proper
> glibc version and for that It needs to be upgraded. :(
This problem has been fixed in the current nightly build of the 5.1.X
family.

Sylvestre



sylvestre sylvestre
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Le lundi 14 septembre 2009 à 15:08 +0530, Sumit Adhikari a écrit :
> Got it now. This time it is very organized. Thanks for this info. By
> the way, do you have any document for so many APIs

Yep, you will find examples here:
modules/call_scilab/examples/basicExamples
and:
modules/call_scilab/examples/call_scilab/

And you will find a documentation in the Scilab help called "Compile and
run with Call Scilab" which explains how to build an application based
on Scilab under the various operating system.

However, please note that in the version 5.2 of Scilab, we are going to
introduce a new API called api_scilab which creates a consistent API to
manage Scilab data. This API handles both code in the gateway (ie,
extends Scilab features) and in call_scilab (ie, call the Scilab engine
from a thirdparty application).
Therefor, the examples above will be updated in a near future (probably
for the version 5.2).

Sylvestre




> Regards,
> Sumit
>
> On Mon, Sep 14, 2009 at 1:26 PM, Sylvestre Ledru
> <[hidden email]> wrote:
>         Le lundi 14 septembre 2009 à 13:24 +0530, Sumit Adhikari a
>         écrit :
>         > Hmm, I know. But my limitation is that my systemc dosent
>         have proper
>         > glibc version and for that It needs to be upgraded. :(
>        
>         This problem has been fixed in the current nightly build of
>         the 5.1.X
>         family.
>        
>         Sylvestre
>        
>        
>


Sumit Adhikari Sumit Adhikari
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Thanks, however I can see with -nwni option this new version is not listning to my old scripts. All are issuing errors to any graphical function call
(like plot()) :(. I was so happy with this feature of my older versions. Do I need to set something to get this feature back in my new version ?
Best Regards,
Sumit

On Mon, Sep 14, 2009 at 4:35 PM, Sylvestre Ledru <[hidden email]> wrote:
Le lundi 14 septembre 2009 à 15:08 +0530, Sumit Adhikari a écrit :
> Got it now. This time it is very organized. Thanks for this info. By
> the way, do you have any document for so many APIs

Yep, you will find examples here:
modules/call_scilab/examples/basicExamples
and:
modules/call_scilab/examples/call_scilab/

And you will find a documentation in the Scilab help called "Compile and
run with Call Scilab" which explains how to build an application based
on Scilab under the various operating system.

However, please note that in the version 5.2 of Scilab, we are going to
introduce a new API called api_scilab which creates a consistent API to
manage Scilab data. This API handles both code in the gateway (ie,
extends Scilab features) and in call_scilab (ie, call the Scilab engine
from a thirdparty application).
Therefor, the examples above will be updated in a near future (probably
for the version 5.2).

Sylvestre




> Regards,
> Sumit
>
> On Mon, Sep 14, 2009 at 1:26 PM, Sylvestre Ledru
> <[hidden email]> wrote:
>         Le lundi 14 septembre 2009 à 13:24 +0530, Sumit Adhikari a
>         écrit :
>         > Hmm, I know. But my limitation is that my systemc dosent
>         have proper
>         > glibc version and for that It needs to be upgraded. :(
>
>         This problem has been fixed in the current nightly build of
>         the 5.1.X
>         family.
>
>         Sylvestre
>
>
>


sylvestre sylvestre
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Le mardi 15 septembre 2009 à 10:31 +0530, Sumit Adhikari a écrit :
> Thanks, however I can see with -nwni option this new version is not
> listning to my old scripts. All are issuing errors to any graphical
> function call
> (like plot()) :(. I was so happy with this feature of my older
> versions. Do I need to set something to get this feature back in my
> new version ?
-nw is your friend.
Starting with Scilab 5.2, we also introduced a dedicated binary for
this:
scilab-adv-cli which is an equivalent to -nw and scilab-cli an
equivalent to -nwni

Sylvestre

> Best Regards,
> Sumit



Sumit Adhikari Sumit Adhikari
Reply | Threaded
Open this post in threaded view
|

Re: Reg :: Integration of Scilab-4.2.1 with C++ from Linux

Thanks a lot :)
Regards,
Sumit

On Tue, Sep 15, 2009 at 12:56 PM, Sylvestre Ledru <[hidden email]> wrote:
Le mardi 15 septembre 2009 à 10:31 +0530, Sumit Adhikari a écrit :
> Thanks, however I can see with -nwni option this new version is not
> listning to my old scripts. All are issuing errors to any graphical
> function call
> (like plot()) :(. I was so happy with this feature of my older
> versions. Do I need to set something to get this feature back in my
> new version ?
-nw is your friend.
Starting with Scilab 5.2, we also introduced a dedicated binary for
this:
scilab-adv-cli which is an equivalent to -nw and scilab-cli an
equivalent to -nwni

Sylvestre

> Best Regards,
> Sumit