From: Vipul R. <vip...@gm...> - 2011-07-15 22:00:34
|
Hi Sam, Firstly, thanks for your reply. However, in our case, we are looking at around 130 classes, and moreover, there is a pressing need to keep them in their divided and modular form for code understand-ability and maintainability. Aren't their any other alternatives? Regards, Vipul On Sat, Jul 16, 2011 at 1:29 AM, Sam Hendley <she...@gr...>wrote: > I think the easiest way to do this is merge all of the ".i" files together > into a single file. Usually there is only one .i file per system, we wrapped > a protocol library with around 20 classes with one file. > > Sam > > On Fri, Jul 15, 2011 at 1:48 PM, Vipul Raheja <vip...@gm...>wrote: > >> Hi, >> >> I have been working on Swig-Python wrapping of OSSIM, a great tool for >> image processing and analysis. After creating respective wrappers (.i files) >> for different classes, I was able to create (for each respective .i file), a >> (.so) library and access the functionality of the earlier C++ libraries in >> Python. But one .i wrapper file and one C++ source file compile into one .so >> library. >> >> So now I've got many .so libraries that I'd like to combine into one >> shared library so that it doesn't depend on the original .so files anymore. >> Say I have a.so and b.so. Can I produce c.so as a single shared library with >> all the functions exported by a and b, of course resolving all >> intra-dependencies (i.e. all functions of b.so called by a.so and the other >> way around)? >> >> Help greatly appreciated. >> >> Regards, >> Vipul Raheja >> >> >> ------------------------------------------------------------------------------ >> AppSumo Presents a FREE Video for the SourceForge Community by Eric >> Ries, the creator of the Lean Startup Methodology on "Lean Startup >> Secrets Revealed." This video shows you how to validate your ideas, >> optimize your ideas and identify your business strategy. >> http://p.sf.net/sfu/appsumosfdev2dev >> _______________________________________________ >> Swig-user mailing list >> Swi...@li... >> https://lists.sourceforge.net/lists/listinfo/swig-user >> >> > |