Hi,

I've got a C extension structured roughly like:

package/
  src/
    Makevars
    foo.c
    some-lib/...
    some-other-lib/..

where foo.c and Makevars define dependencies on some-lib and
some-other-lib. Currently I'm having
Makevars configure;make install some-lib and some-other-lib into a local
build directory, which produces
shard libraries that ultimately I reference for foo.o in PKG_LIBS.

I'm concerned about distribution. I've setup the appropriate magic with
rpath for the packages .so (meaning
that when the final .so is produced the dynamic libraries dependencies on
some-lib and some-other-lib
will prefer the location built in src/some-lib/... and
src/some-other-lib/... But does this preclude me from
being able to distribute a binary package? If I do want to build a binary
distribution, is there a way I can
package up everything needed, not just the resulting .so?

Or, are there better ways to bundle extension-specific third party
dependencies? ;) I'd rather not have
my users have to install obscure libraries globally on their systems.


Thanks!


Tyler

	[[alternative HTML version deleted]]

