File: G_make.man

package info (click to toggle)
scilab 2.4-1
  • links: PTS
  • area: non-free
  • in suites: potato, slink
  • size: 55,196 kB
  • ctags: 38,019
  • sloc: ansic: 231,970; fortran: 148,976; tcl: 7,099; makefile: 4,585; sh: 2,978; csh: 154; cpp: 101; asm: 39; sed: 5
file content (40 lines) | stat: -rw-r--r-- 1,270 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
.TH G_make 1 "May 1995" "Scilab Group" "Scilab Function"
.so ../sci.an
.SH NAME
G_make - call make or nmake 
.SH CALLING SEQUENCE
.nf
Rfiles=G_make(files,dllname)
.fi
.SH PARAMETERS
.TP 10
files
: a character string or a vector of character string.
.TP 10
dllname 
: a character string.
.TP 10
Rfiles
: vector of character string. \fVRfiles\fR can be used as a first
argument when calling \fVaddinter\fR function.
.SH DESCRIPTION
On Unix like systems (i.e unix or windows/gcwin32) \fVG_make\fR calls
the \fVmake\fR utility for building target \fVfiles\fR and returns
the value of \fVfiles\fR in the variable \fVRfiles\fR. On windows platforms, (i.e when
Scilab was compiled with Microsoft VisualC++). \fVG_make\fR calls
the \fVnmake\fR utility for building target \fVdllname\fR and it
returns the value of \fVdllname\fR in the variable \fVRfiles\fR. 
Of course \fVG_make\fR will work if apropriate Makefiles are 
provided in the current Scilab directory. 
.LP
\fVG_make\fR can be used to provide OS independant call to addinter. 
and such examples can be found in the directory
\fVSCIDIR/examples/addinter-examples\fR
.nf 
files=G_make(['/tmp/ex1cI.o','/tmp/ex1c.o'],'ex1c.dll');// compilation 
addinter(files,'foobar','foubare'); // link 
.fi 
.SH SEE ALSO
addinter,