Hi, Ihor!
Yes, rtp.io has no packaging logic at the moment, not being mentioned in
either the control
<https://github.com/OpenSIPS/opensips/blob/3.6/packaging/debian/control>
or rules
<https://github.com/OpenSIPS/opensips/blob/3.6/packaging/debian/rules>
files, so it simply gets skipped during the package builds.
To fix this, we would need a rtpproxy project clone during the build
(git submodule?), then build it as static library flavor (as
"librtpproxy.a" file, using --enable-librtpproxy, and not just
"rtpproxy" binary). Then, the rtp.io module would simply build against
the ".a" file, finally producing "rtp.io.so". The rest is history :)
Could be worth putting up a feature request for this, it also seems to
be a good-first-issue candidate (couple hours of work).
Best regards,
On 21.08.2025 16:57, Ihor Olkhovskyi wrote:
Hello!
As I got, in a debian repo there is no rtp.io <http://rtp.io> package?
Or I've missed something?
--
Best regards,
Ihor (Igor)
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Liviu Chircu
www.opensips-solutions.com |www.siphub.com
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
