I think you've misunderstood me: you can't statically link an .so library to another .so library, but you can link one or more .o files into a single .so library.
Does that make it clearer?
In any case, if you really have to, you can always distribute the additional .so file with the perl/xs/so files.
Other than pure curiousity, I don't really see a reason you'd want to do this.
| [reply] |
Ok, if I build an application that has a shared object that can be installed, that .so is made up of one or more .o files in some separate build directory. Is there a way to append the .o files to the Perl module .so, or does it all have to be done at once.
The reason this needs to be done is I do not want to hard-code an LD_RUN_PATH or a LD_LIBRARY_PATH to run the apps. There is also the problem of different versions of the libraries. I want only my versions to work with my distributed Perl, so I will not be installing any external shared libraries with my apps.
| [reply] |
If I read ExtUtils::MakeMaker's documentation correctly, you may be able to add static objects to the OBJECT parameter of WriteMakefile() in your Makefile.PL
WriteMakefile(
# stuff
OBJECT => 'mylib.o anotherlib.o $(BASEEXT)$(OBJ_EXT)'
# more stuff
);
| [reply]
[d/l]
[select] |