translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
library
    microhttpd0.9.73
    QmQRrfpawuRt8zLyyusi79W9c2hYV57aLSemswZVwtGsJC
    5dsR32Biazw5Wytgpg5E244ZwhRgdD
      QmQRrfpawuRt8zLyyusi79W9c2hYV57aLSemswZVwtGsJC
      5dsR32Biazw5Wytgpg5E244ZwhRgdD

      • Details
      • Build
      • Files
      • History
        • Summary

          A small C library that is supposed to make it easy to run an HTTP server as part of another application.

          Website

          https://www.gnu.org/software/libmicrohttpd/

          License

            Environment

            linux

            Architecture

            x86-64

            Versions

            • 0.9.73

            DependenciesHelp

            This section shows a list of objects the current object is dependent upon in order to be used.

            For dependencies that are only relevant as part of the build or runtime of the object, it is best to describe those local to those sections.

            • library

              gnutls

              3.x

            BuildHelp

            This section tracks information useful to describing how to build this object.

            Dependencies

            • collection

              build

              1.0

            • compiler

              g++

              >5

            • application

              curl

              7.x

            Resources

            • libmicrohttpd-0.9.73.tar.gz

              application/gzip

              libmicrohttpd 0.9.73 Source Code

              https://ftp.gnu.org/gnu/libmicrohttpd/libmicrohttpd-0.9.73.tar.gz

              QmZwMfToC5cN5QzmpdkVjxQSBUtB8Hcx1RfshEQX8MKJmQ

              Qmdz39zgEtszLpNKQy2MqvChbhNMAvRrtTmxctn1siY9As

              QmZLp7GPViuzxeSpwbvxZcGzd28NW1joeDCxVNaQjG9Kky

              download

            Command

            • /bin/bash
            • build.sh

            Build Environment

            • linux
            • x86-64

            InstallationHelp

            Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

            This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

            There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

            ActionSourceDestinationSummary
            Linkusr/lib/usr/lib

            N/A

            Linkusr/include/usr/include

            N/A

            Linkusr/share/usr/share

            N/A

            No files will be installed.

            Share

            • URL

              Copy
            • Embed Link

              Copy
            • QR Code

          • JavaScript must be enabled.

            There was an error retrieving this content.

            The content could not be found.

          • JavaScript must be enabled.

            There was an error retrieving this content.

            The content could not be found.

          • JavaScript must be enabled.

            There was an error retrieving this content.

            The content could not be found.

          Confirm
          Do you wish to proceed?

          Confirm message?