translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
runtime
    gobject-introspection1.68.0
    QmbacozUNnJW8xWCmDEWtzL9fQZV8PSpYeWXoYFxk84Mv4
    5drBbQBVoErA1WVcWqfK5bS5qbA3om
      QmbacozUNnJW8xWCmDEWtzL9fQZV8PSpYeWXoYFxk84Mv4
      5drBbQBVoErA1WVcWqfK5bS5qbA3om

      • Details
      • Build
      • Files
      • History
        • Summary

          A middleware layer between C libraries and language bindings.

          Website

          https://wiki.gnome.org/Projects/GObjectIntrospection

          License

          • LGPL 2.0
          • GPL 2.0

          Environment

          linux

          Architecture

          x86-64

          GObject introspection is a middleware layer between C libraries (using GObject) and language bindings. The C library can be scanned at compile time and generate a metadata file, in addition to the actual native C library. Then at runtime, language bindings can read this metadata and automatically provide bindings to call into the C library.

          Versions

          • 1.54.1

          • 1.68.0

          Related

          • maintainer

            occam

          Includes

          • application

            g-ir-compiler

          • application

            g-ir-generate

          • application

            g-ir-inspect

          • application

            g-ir-scanner

          • application

            g-ir-annotation-tool

          • application

            g-ir-doc-tool

          BuildHelp

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

          Dependencies

          • application

            gtk-doc

            1.x

          • language

            python

            3.7.x

          • python-library

            Markdown

            3.x@3.7

          • python-library

            Mako

            1.x@3.7

          • collection

            build

            1.0

          • compiler

            g++

            >5

          • application

            cmake

            3.x

          • collection

            gettext

            0.19.x

          • collection

            autoconf

            2.69

          • collection

            automake

            1.15.x

          • application

            m4

            1.x

          • application

            libtool

            2.x

          • application

            flex

            2.x

          • application

            bison

            3.x

          • library

            cairo

            1.x

          • library

            glib2

            >=2.58.0

          • application

            meson

            0.x

          • data

            tzdata

            x

          • application

            gtk-doc

            1.x

          • python-library

            Sphinx

            4.x@3.7

          Resources

          • gobject-introspection

            git

            GNOME gobject-introspection Source Code Repository

            https://git.gnome.org/browse/gobject-introspection

            QmcUcwnHMck8jrGMfgAZ7KdkCJYYci6rXYxHdVvNJX2vqX

            QmUC5Jym2t4eqEU3R39saNcGoALByHWnYjFvqiiZ44PwWc

            342dc78977eef2f444b988a46e435fbafbdcb165

            Copy
          • glib

            git

            GNOME glib Source Code Repository

            https://gitlab.gnome.org/GNOME/glib.git

            QmQLQAowuzmPKj2MNczgVkz8HCSopdbTkcGVANFKPu33WL

            QmWL7Th9vxjaXjreUkU5ScvCwguHoNwksUYRoGibKDbnE7

            a58a47fd6d3da5ffb28809f212971748667dfb3c

            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/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?