translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
library
    xcb-proto1.12
    QmYmScUmqqzWLttFH4o757ATyRfScGbjPggLpUQctvdfSw
    5drr6roqA8V613T4abdvyECz3Z3G1E
      QmYmScUmqqzWLttFH4o757ATyRfScGbjPggLpUQctvdfSw
      5drr6roqA8V613T4abdvyECz3Z3G1E

      • Details
      • Build
      • Files
      • History
        • Summary

          Header files for the X11 XML-XCB Protocol used by the xcb library.

          Environment

          linux

          Architecture

          x86-64

          Versions

          • 1.12

          • 1.14

          Related

          • maintainer

            occam

          BuildHelp

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

          Dependencies

          • language

            python2

            2.7.x

          • collection

            build

            1.0

          • compiler

            g++

            >5

          • library

            xorg-macros

            1.x

          Resources

          • xcb-proto-1.12.tar.gz

            application/gzip

            libxcb-proto 1.12 Source Code

            https://www.x.org/releases/individual/xcb/xcb-proto-1.12.tar.gz

            QmUT3ADg8e6ynGL3hDw5bBFN3Qwi2XuAVvjQkXiQesQhrs

            QmUQLGra3RPyhp2ujd2dX83X1bgYmNLfFWp7ng9hs3SNa7

            QmcKCh8EwQ5KEhGkgQ3iuxiCYW3WWQY48N9pMS3JH4x9dA

            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?