• 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
application
    glib-genmarshal2.68.3
    QmanbnJdnXtx1MnzMzq3sAEBdYRr6ieBTjfW3BxRw15roi
    5drUAamntJxuMXTfCQmtsZWAnoVghN
      QmanbnJdnXtx1MnzMzq3sAEBdYRr6ieBTjfW3BxRw15roi
      5drUAamntJxuMXTfCQmtsZWAnoVghN

      • Details
      • Run
      • Files
      • History
        • Website

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

          License

          • LGPL 2.1

          Environment

          linux

          Architecture

          x86-64

          glib-genmarshal is a small utility that generates C code marshallers for callback functions of the GClosure mechanism in the GObject sublibrary of GLib. The marshaller functions have a standard signature, they get passed in the invoking closure, an array of value structures holding the callback function parameters and a value structure for the return value of the callback. The marshaller is then responsible to call the respective C code function of the closure with all the parameters on the stack and to collect its return value.

          glib-genmarshal takes a list of marshallers to generate as input. The marshaller list is either read from files passed as additional arguments on the command line; or from standard input, by using - as the input file.

          Marshaller list format The marshaller lists are processed line by line, a line can contain a comment in the form of or a marshaller specification of the form

          RTYPE:PTYPE RTYPE:PTYPE,PTYPE RTYPE:PTYPE,PTYPE,PTYPE

          The RTYPE part specifies the callback's return type and the PTYPEs right to the colon specify the callback's parameter list, except for the first and the last arguments which are always pointers.

          Parameter types Currently, the following types are supported:

          VOID indicates no return type, or no extra parameters. If VOID is used as the parameter list, no additional parameters may be present.

          BOOLEAN for boolean types (gboolean)

          CHAR for signed char types (gchar)

          UCHAR for unsigned char types (guchar)

          INT for signed integer types (gint)

          UINT for unsigned integer types (guint)

          LONG for signed long integer types (glong)

          ULONG for unsigned long integer types (gulong)

          INT64 for signed 64bit integer types (gint64)

          UINT64 for unsigned 64bit integer types (guint64)

          ENUM for enumeration types (gint)

          FLAGS for flag enumeration types (guint)

          FLOAT for single-precision float types (gfloat)

          DOUBLE for double-precision float types (gdouble)

          STRING for string types (gchar*)

          BOXED for boxed (anonymous but reference counted) types (GBoxed*)

          PARAM for GParamSpec or derived types (GParamSpec*)

          POINTER for anonymous pointer types (gpointer)

          OBJECT for GObject or derived types (GObject*)

          VARIANT for GVariant types (GVariant*)

          NONE deprecated alias for VOID

          BOOL deprecated alias for BOOLEAN

          Versions

          • 2.54.1

          • 2.68.3

          Related

          • maintainer

            occam

          • within

            library

            glib2

          • packaged with

            application

            gtester

          • packaged with

            application

            gobject-query

          • packaged with

            application

            gio

          • packaged with

            application

            gresource

          • packaged with

            application

            gio-querymodules

          • packaged with

            application

            glib-compile-schemas

          • packaged with

            application

            glib-compile-resources

          • packaged with

            application

            gsettings

          • packaged with

            application

            gdbus

          • packaged with

            application

            gapplication

          • packaged with

            application

            gtester-report

          • packaged with

            application

            glib-mkenums

          • packaged with

            application

            gdbus-codegen

          • packaged with

            application

            glib-gettextize

          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

            zlib

            1.x

          • library

            ffi

            3.x

          • collection

            util-linux

            2.x

          • library

            elf

            0.x

          • language

            python

            3.x

          • library

            pcre

            8.x

          RunHelp

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

          Command

          • /usr/bin/glib-genmarshal

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