This is what I sent to Gary on 06/27
Summary
=======
SWIG is a software development tool that connects programs written in
C and C++ with a variety of high-level programming languages. SWIG is
used with different types of languages including common scripting
languages
such as Perl, PHP, Python, Tcl and Ruby. The list of supported languages
also includes non-scripting languages such as C#, Common Lisp
(CLISP, Allegro CL, CFFI, UFFI), Java, Lua, Modula-3, OCAML, Octave
and R.
Also several interpreted and compiled Scheme implementations
(Guile, MzScheme, Chicken)are supported. SWIG is most commonly used to
create high-level interpreted or compiled programming environments, user
interfaces, and as a tool for testing and prototyping C/C++ software.
SWIG can also export its parse tree in the form of XML and Lisp
s-expressions. SWIG may be freely used, distributed, and modified for
commercial and non-commercial use.
SWIG 1.3.35 will be integrated into the SFW consolidation as part of
this proposal, and will be installed as SUNWswig.
This project requests a minor release binding.
Dependencies
============
SUNWgccruntime GCC Runtime libraries
SUNWlibmsr Math & Microtasking Libraries (Root)
Interfaces
==========
Stability classification Uncommitted for all exported interfaces. Man
pages are included in the case materials directory.
Exported Interfaces
-------------------
/usr/bin/swig Command
/usr/share/man/man1/swig.1 Man page
Imported Interfaces
-------------------
None
The following additional installed files are not interface.
Additional documentation
-------------------
/usr/share/swig/1.3.35/doc/manual/SWIGDocumentation.pdf
/usr/share/swig/1.3.35/doc/manualswigpdf.book
In /usr/share/swig/1.3.35/doc/manual
Allegrocl.html Lua.html Ruby.html
Arguments.html Modula3.html SWIG.html
CSharp.html Modules.html
SWIGDocumentation.html
Chicken.html Mzscheme.html SWIGPlus.html
Contents.html Ocaml.html
Scripting.html
Contract.html Octave.html Sections.html
Customization.html Perl5.html Tcl.html
Extending.html Php.html Typemaps.html
Guile.html Pike.html Varargs.html
Introduction.html Preface.html Warnings.html
Java.html Preprocessor.html Windows.html
Library.html Python.html index.html
Lisp.html R.html
in /usr/share/swig/1.3.35/doc/devel
cmdopt.html index.html scanner.html
engineering.html internals.html tree.html
file.html parm.html wrapobj.html
Reference Documents
===================
[1] http://www.swig.org/doc.html
man page which installs
sem17% man swig
Reformatting page. Please Wait... done
swig 1.3.35 Last change: 19 Jun 2008 1
User commands swig(1)
NAME
swig <options> filename
SYNOPSIS
/usr/bin/swig -help [ For commandline help ]
DESCRIPTION
swig - The Simplified Wrapper and Interface Generator (swig)
is an open source code interface compiler that connects pro-
grams written in C and C++ with scripting languages such as
Perl, Python, Ruby, and Tcl. It works by taking the declara-
tions found in C/C++ header files and using them to generate
the wrapper code that scripting languages need to access the
underlying C/C++ code. In addition, SWIG provides a variety
of customization features that let you tailor the wrapping
process to suit your application.
SWIG is used in a number of ways:
Building more powerful C/C++ programs. Using SWIG, you can
replace the main() function of a C program with a scripting
interpreter from which you can control the application. This
adds quite a lot of flexibility and makes the program "pro-
grammable." That is, the scripting interface allows users
and developers to easily modifiy the behavior of the program
without having to modify low-level C/C++ code. The benefits
of this are numerous. In fact think of all of the large
software packages that you use every day---nearly all of
them include special a macro language, configuration
language, or even a scripting engine that allows users to
make customizations.
Rapid prototyping and debugging. SWIG allows C/C++ programs
to be placed in a scripting environment that can be used for
testing and debugging. For example, you might test a library
with a collection of scripts or use the scripting inter-
preter as an interactive debugger. Since SWIG requires no
modifications to the underlying C/C++ code, it can be used
even if the final product does not rely upon scripting.
Systems integration. Scripting languages work fairly well
for controlling and gluing loosely-coupled software com-
ponents together. With SWIG, different C/C++ programs can be
turned into scripting language extension modules. These
modules can then be combined together to create new and
interesting applications.
Construction of scripting language extension modules. SWIG
can be used to turn common C/C++ libraries into components
for use in popular scripting languages. Of course, you will
still want to make sure that no-one else has already created
a module before doing this.
swig 1.3.35 Last change: 19 Jun 2008 1
User commands swig(1)
SEE ALSO
Installed documentation: /usr/local/share/swig/1.3.35/doc
Complete online documentation in HTML and PDF formats for
swig:
User Manual: http://www.swig.org/Doc1.1/HTML/Contents.html
Developer Doc: http://www.swig.org/Doc1.3/index.html
Quick start Tutorial: http://www.swig.org/tutorial.html
SWIG WIKI: http://en.wikipedia.org/wiki/SWIG
The Latest full source download:
http://www.swig.org/download.html
AUTHOR
swig was originally written by Dave Beazley, and is now
maintained and developed by an team of developers see:
http://www.swig.org/guilty.html. Further details are avail-
able at http://www.swig.org/index.html. swig is released
under the swig License.
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
_______________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE|
|_______________________________________
| Availability | SUNWswig |
|_______________________________________
| Interface Stability| Volatile |
|____________________|_________________|
NOTES
Source for swig is available on http://opensolaris.org.
swig 1.3.35 Last change: 19 Jun 2008 2
Alan Coopersmith wrote:
> Your ARC sponsor should have given that to you. You do know it's your
> job to find someone to be your ARC sponsor and get them to submit
> your case, right?
>
> -Alan Coopersmith- alan.coopersmith at sun.com
> Sun Microsystems, Inc. - X Window System Engineering
>
>
> Bruce Rothermal wrote:
>> I don't know I'm still waiting for some feedback on at least that. Is
>> there some alias where this is communicated. The project is swig
>> package SUNWswig.
>>
>> Bruce
>>
>>
>> David.Comay at Sun.COM wrote:
>>>> I was just wondering how many people are sitting idle on porting
>>>> projects waiting on ARC process and could we come up with some
>>>> ideas on
>>>> how to make this work better. I'm at about 6 weeks now.
>>> What's the case number of the project in question?
>>>
>>> dsc
>>
>> _______________________________________________
>> sfwnv-discuss mailing list
>> sfwnv-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
