On 04/05/15 13:55, Christian Weisgerber wrote: > Quote: | GNU libmicrohttpd offers a C library that provides a > compact API | and implementation of an HTTP 1.1 web server (HTTP > 1.0 is also | supported). GNU libmicrohttpd only implements the > HTTP protocol. | The main application must still provide the > application logic to | generate the content. > > Some comments on the port: * SPDY is disabled because support is > still "early alpha" and meanwhile SPDY has already been obsoleted > by HTTP 2.0. * HTTPS is disabled because it pulls in libgnutls and > libgcrypt, which aren't so micro any more. Can be enabled once > something needs it. * Good test coverage requires curl, zzuf, and > socat, but unfortunately these must already be installed at build > time and can't be TEST_DEPENDS. >
There is a version in openbsd-wip. SPDY was disabled, but gnutls enabled, OpenVAS also in openbsd-wip depends on libmicrohttp. https support is a must have for OpenVAS. Mine is 0.9.38, your's is a later version 0.9.39. OpenVAS needs an update also. I had one minor issue install/uninstall with .info files, still to resolve. $ sudo pkg_delete -a install-info: warning: no entries found for `/usr/local/info/libmicrohttpd-tutorial.info'; nothing deleted libffi-3.0.13p0:libmicrohttpd-0.9.38: ok libffi-3.0.13p0:gnutls-3.2.21: ok libffi-3.0.13p0:p11-kit-0.22.1p0: ok libffi-3.0.13p0: ok libnettle-2.7.1p1: ok gettext-0.19.4:libgcrypt-1.6.3: ok gettext-0.19.4:libgpg-error-1.18: ok gettext-0.19.4: ok libiconv-1.14p2: ok libtasn1-4.4: ok gmp-5.0.2p3: ok Read shared items: ok Have to run all the tests on this, has been known to fail in the past. Having curl, zzuf, socat during build really doesn't matter, as long as not there at runtime.
