Re: [Swig-user] One vs Many interface files

[Tomas W. <Tom...@hi...>]

At least with Python there can only be one interface file defining %module per extension library, so if you're using one interface per source file you need to compile each source file into a separate extension. This is probably not what you want. Identify instead the required interface used from Python and include only that in the interface file.

/Tomas W.
________________________________________
Från: Bob Rossi [bo...@br...]
Skickat: den 19 november 2010 00:20
Till: Swi...@li...
Ämne: [Swig-user] One vs Many interface files

Hi,

I'm thinking about using SWIG to extend some C++ to python.
My C++ application is built from many different source files.

Some simple questions,

Does it make sense to use one interface file per source file,
or one interface file for the application?

If you use multiple interface files, are the arguments/return
types of the generated python files compatible between the
different generated python files? (It seems like some of the
python files would understand certain types, and others
would not)

Does anyone have a simple example using boost shared pointers?
The examples directory has a smartptr test, but that's not
exactly the same.

Thanks,
Bob

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Swig-user mailing list
Swi...@li...
https://lists.sourceforge.net/lists/listinfo/swig-user