Package: libcivetweb1 Version: 1.13+dfsg-5 Severity: wishlist X-Debbugs-Cc: cla...@mathr.co.uk
Dear Maintainer, * What led up to the situation? I wanted to write a websocket server using civetweb packaged in Debian. * What was the outcome of this action? Debian civetweb is not built with websockets support. I managed to rebuild the package locally with websockets support by adding -DCIVETWEB_ENABLE_WEBSOCKETS=ON to CMAKE_EXTRA_FLAGS in debian/rules, adding extra lines to debian/libcivetweb1.symbols like mg_websocket_client_write@Base 1.13+dfsg-5 mg_websocket_write@Base 1.13+dfsg-5 I'm not sure if other changes need to be made (e.g. library version bump for changed ABI?). Thanks for your consideration, -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcivetweb1 depends on: ii libc6 2.31-12 ii libgcc-s1 10.2.1-6 ii libstdc++6 10.2.1-6 libcivetweb1 recommends no packages. libcivetweb1 suggests no packages. -- no debconf information
