• 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
    xkbcommon1.4.0
    QmUWao9cPVrygn1CnXa7XdnZYAJF2iEuF3xKrvgfpcJVWd
    5dqvAZWvibGJ2dBAkHXqDX7J8tMBNW
      QmUWao9cPVrygn1CnXa7XdnZYAJF2iEuF3xKrvgfpcJVWd
      5dqvAZWvibGJ2dBAkHXqDX7J8tMBNW

      • Details
      • Build
      • Files
      • History
        • Summary

          A library for handling keyboard descriptions.

          Website

          https://xkbcommon.org/

          License

          • MIT/X11

          Environment

          linux

          Architecture

          x86-64

          xkbcommon is a library to handle keyboard descriptions, including loading them from disk, parsing them and handling their state. It's mainly meant for client toolkits, window systems, and other system applications; currently that includes Wayland, kmscon, GTK+, Qt, Clutter, KWin and more. It is also used by some XCB applications for proper keyboard support.

          Versions

          • 0.7.2-without-x11

          • 0.7.2

          • 1.4.0

          Related

          • maintainer

            occam

          Includes

          • library

            xkbcommon-x11

          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.

          • data

            xkeyboard-config

            2.x

          BuildHelp

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

          Dependencies

          • collection

            build

            1.0

          • compiler

            g++

            >5

          • library

            Xcb

            1.x

          • library

            jpeg-turbo

            2.x

          • library

            wayland

            1.x

          • library

            wayland-protocols

            1.x

          • application

            meson

            0.x

          • collection

            gettext

            0.19.x

          • collection

            autoconf

            2.x

          • collection

            automake

            1.x

          • application

            libtool

            2.x

          • application

            bison

            3.x

          • application

            flex

            2.x

          • application

            doxygen

            1.x

          Resources

          • libxkbcommon

            git

            libxkbcommon Source Code Repository

            https://github.com/xkbcommon/libxkbcommon

            QmeywdFFJ27vbFJXbJU7XCktpLSEw5gSaxZe9biuJzZiAC

            QmSgNWz4GT3Fc6JBmxSr7gtDQLMeFF3PdX3dTTrhUujC8z

            ea6580cc3913d93655ecf92a5913de652315efc3

            Copy

          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/lib64/usr/lib64

          N/A

          Linkusr/include/usr/include

          N/A

          Linkusr/share/usr/share

          N/A

          Linkusr/bin/usr/bin

          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?