On Sat, 27 Sep 2003 17:40:34 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
Now it should be said that my understanding of SWIG doesn't go much beyond the fact that it is a system for interfacing two languages - in our case presumeably C++ and Python. I've downloaded a tarball and am currently reading the doc's. VZ> Yes. Fixing Python is easy but not trivial. There are 2 posssibilities: VZ> VZ> 1. simple but not very interesting: update .i files manually, i.e. simply VZ> integrate the changes from .h files into them Is this hard to do? I have not looked at it at all yet. VZ> 2. try new SWIG (1.3.19?) which is supposed to be able to directly parse .h VZ> files and get rid of .i completely or, maybe, keep them but just for VZ> SWIG directives (i.e. we could tell it to ignore some methods or rename VZ> some others) Would we be better off first trying to use the SWIG that is used in wxPython as I understand Robin has specially modified it to be used with wxWindows? It also at least comes in the wxWindows CVS tree. I would ask Robin but since I do not understand any of the issues, it would not be much of a useful discussion. Perhaps Vadim you could ask Robin what modifications he has made before we go out and reinvent the wheel and introduce another dependency we might not need? TIA Dr. QA ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
