• Login
    • Report A Bug
    • System Information
    • System Tests
    • System Policies
    • Code Documentation
    • Occam Source Code
    • Web Client Source Code
    • About Occam
    • Acknowledgements
    • Guides / Documentation
    • Publications

translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
library
    xextproto7.3.0
    QmSzqSPVJW8vgcUoeq9CyiWuX4AttccpypdSVQ1Ew9aLyr
    5dtisXG7K9G6WPtJx5S9wUPzWNvqfM
      QmSzqSPVJW8vgcUoeq9CyiWuX4AttccpypdSVQ1Ew9aLyr
      5dtisXG7K9G6WPtJx5S9wUPzWNvqfM

      • Details
      • Build
      • Files
      • History
        • Summary

          Header files for several common X11 Extensions.

          Environment

          linux

          Architecture

          x86-64

          Versions

          • 7.3.0

          Related

          • maintainer

            occam

          BuildHelp

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

          Dependencies

          • collection

            build

            1.0

          • compiler

            g++

            >5

          • library

            xorg-macros

            1.x

          Resources

          • xextproto-7.3.0.tar.gz

            application/gzip

            xextproto 7.3.0 Source Code

            https://www.x.org/releases/individual/proto/xextproto-7.3.0.tar.gz

            QmUHaw5XspxFghgmuSDFBcxh4vVLnSa3y2JG76jhNYvRn2

            QmVypHRAeuSFxPYAGu5mB5dUVcPUS62BFkwVhrGWYnQ5FW

            QmQAUJozma9iazxo2zpWiD7cESdELEHCJ5pCwEvWp58ct4

            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

          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?