From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902944

Hi!

We've got several local kamailio modules, and it would be nice to be
able to build them separately and not have to hook them into the
kamailio source and build systems. I suppose others might find this
useful too.

I started pondering what adding support for this would imply, and I
think the first step is whether this is something you think upstream
and you'd be happy supporting? It could be that the internal interfaces
are completely unstable and providing this might be a support nightmare,
for example, or other similar concerns.

I think what would be needed is:

• Support installing the library .so symlinks into the -dev package.
  (The module .so I think would need to stay in the main and module
  packages, because some stuff loads them as module.so directly?)
• Support installing the kamailio core, library and module .h files
  into the -dev package. AFAIUI modules can have inter-module
  dependencies and they might use interfaces from both kamailio core
  itself, the shared libraries or other modules.
• Provide a pkg-config file with the necessary compile and link runes
  (-I, -L, -rpath and similar) to be able to build 3rd party modules
  easily.

While checking this, I noticed there's a src/lib/Makefile.defs, which
has a TYPE variable to install headers and similar, but it does not
appear to be currently used?

Thanks,
Guillem

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.