g-ir-scanner (1) - Linux Man Pages
g-ir-scanner: extracting C metadata from sources and headers
NAMEg-ir-scanner - extracting C metadata from sources and headers
SYNOPSISg-ir-scanner [OPTION...] FILES...
DESCRIPTIONg-ir-scanner is a tool which generates GIR XML files by parsing headers and introspecting GObject based libraries. It is usually invoked during the normal build step for a project and the information is saved to disk and later installed, so that language bindings and other applications can use it. Header files and source files are passed in as arguments on the command line. The suffix determines whether a file be treated as a source file (.c) or a header file (.h). Currently only C based libraries are supported by the scanner.
- Show help options
- If passed, do not print details of normal operation.
- Display warnings for public API which is not introspectable.
- Make warnings be fatal errors.
- This parameters decides which the resulting format will be used. The default value is gir.
- Add the specified introspection dependency to the scanned namespace. NAME is of the form NAMESPACE-VERSION, like Gtk-3.0.
- Add the specified introspection dependency to the scanned namespace. This differs from --include in that it takes a file path, and does not process the pkg-config dependencies (since they may not be installed yet).
- Add a directory to the path which the scanner uses to find GIR files. Can be used multiple times to specify multiple directories
- -i, --library=LIBRARY
- Specifies a library that will be introspected. This means that the *_get_type() functions in it will be called for GObject data types. The name of the library should not contain the leading lib prefix nor the ending shared library suffix.
- -L, --library-path=PATH
- Include this directory when searching for a library. This option can be specified multiple times to include more than one directory to look for libraries in.
- Include this directory in the list of directories to be searched for header files. You need to pass to the scanner all the directories you'd normally pass to the compiler when using the specified source files.
- -n, --namespace=NAME
- The namespace name. This name should be capitalized, eg the first letter should be upper case. Examples: Gtk, Clutter, WebKit.
- Disable usage of libtool for compiling stub introspection binary. Use this if your build system does not require libtool.
- Full path to libtool executable. Typically used for Automake systems.
- The namespace version. For instance 1.0. This is usually the platform version, eg 2.0 for Gtk+, not 2.12.7.
- -p, --program=PROGRAM
- Specifies a binary that will be introspected. This means that the *_get_type() functions in it will be called for GObject data types. The binary must be modified to take a --introspect-dump= option, and to pass the argument to this function to g_irepository_dump.
- Additional argument to pass to program for introspection.
- This option may be specified multiple times. Each one gives a prefix that will be stripped from all C identifiers. If none specified, the namespace will be used. Eg, an identifier prefix of Foo will export the identifier typdef struct _FooBar FooBar; as Foo.Bar.
- This option may be specified multiple times. Each one gives a prefix that will be stripped from all C symbols. Eg, an symbol prefix of foo will export the symbol foo_bar_do_something as Foo.Bar.do_something.
- If specified, the scanner will accept identifiers and symbols which do not match the namespace prefix. Try to avoid using this if possible.
- Name of the file to output. Normally namespace + format extension. Eg, GLib-2.0.gir.
- List of pkg-config packages to get compiler and linker flags from. This option can be specified multiple times to include flags from several pkg-config packages.
- List of pkg-config packages that are provided by the generated gir. This option can be specified multiple times if the gir provides more packages. If not specified, the packages specified with --pkg= will be used.
- Be verbose, include some debugging information.
BUGSReport bugs at http://bugzilla.gnome.org/ in the gobject-introspection product.
HOMEPAGE and CONTACThttp://live.gnome.org/GObjectIntrospection