>From the documentation
16 Working with Modules
When first working with SWIG, users commonly start by creating a single
module. That is, you might define a single SWIG interface that wraps
some set of C/C++ code. You then compile all of the generated wrapper
code into a module and use it.
What's a module ?? Is it a psuedonym for a (shared)library (as in
windows .dll, or *nix .so file)?
What do you mean "compile all of the generated wrapper code into a
module" ?
Do you mean compile the generated wrapper classes and link them together
along with the original classes that they wrap into a shared library?
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects_______________________________________________
Swig-user mailing list
Swig-user@...
https://lists.sourceforge.net/lists/listinfo/swig-user
