Bug #2661
Updated by neels over 6 years ago
I'm wondering why we are actually creating + installed a libosmo-mgcp shared library? Isn't it only used by osmo-mgw? osmo-msc? In that case, it would be best to simply have it as an internal, non-installed static library (like libbsc.a in osmo-bsc/openbsc) instead of installing it into the system. This means there's no API/ABI compatibility to maintain. For the client library (libosmo-mgcp-client), this is of course completely different, and it must be installed and have a stable API/ABI. If there are some smaller utility functions used by e.g. osmo-bsc_nat (which uses -legacy at the moment anyway), then we should try to abstract those out and have only those in the shared library, leaving most mgw code private to the osmo-mgw repository. Please share your thoughts/feedback, particularly neels + dexter.
