Re: [Swig-user] Building Python module on top of Multiple static libraries

[William S F. <ws...@fu...>]

Focus wrote:
> I am trying to use swig to build a python module that will interface 
> with a simple C++ class. Only issue I am running into is that this c++ 
> class has a good number of dep's on static libraries that we wrote. Is 
> there a way to build a sort of "entry point" class so that not all of 
> the libraries need to be shared , or is there a way using gcc to build 
> sort of a mega .so with code from all libs ?  I would like to stay away 
> from having to build shared libs of each one of my deps. 
> 

If your simple C++ class has dependencies on all the other static 
libraries, then you need to link with them when you build your wrapper 
library. Or compile the C++ class into a new library itself (and link it 
against all its dependencies) and then just link with new library.

William