2.1. Normative References

The specifications listed below are referenced in whole or in part by the LSB Desktop specification. Such references may be normative or informative; a reference to specification shall only be considered normative if it is explicitly cited as such. The LSB Desktop specification may make normative references to a portion of these specifications (that is, to define a specific function or group of functions); in such cases, only the explicitly referenced portion of the specification is to be considered normative.

2.2. Informative References/Bibliography

In addition, the specifications listed below provide essential background information to implementors of this specification. These references are included for information only.

3.1. Relevant Libraries

The libraries listed in Table 3-1 shall be available on a Linux Standard Base - Desktop system, with the specified runtime names. This list may be supplemented or amended by the architecture-specific specification.

These libraries will be in an implementation-defined directory which the dynamic linker shall search by default.

6.1. Introduction

A conforming implementation shall support the following GTK+ stack libraries which provide interfaces for creating rich graphical user interface applications.

There are three main parts to the definition of each of these libraries.

The "Interfaces" section defines the required library name and version, and the required public symbols (interfaces and global data), as well as symbol versions, if any.

The "Interface Definitions" section provides complete or partial definitions of certain interfaces where either this specification is the source specification, or where there are variations from the source specification. If an interface definition requires one or more header files, one of those headers shall include the function prototype for the interface.

For source definitions of interfaces which include a reference to a header file, the contents of such header files form a part of the specification. The "Data Definitions" section provides the binary-level details for the header files from the source specifications, such as values for macros and enumerated types, as well as structure layouts, sizes and padding, etc. These data definitions, although presented in the form of header files for convenience, should not be taken a representing complete header files, as they are a supplement to the source specifications. Application developers should follow the guidelines of the source specifications when determining which header files need to be included to completely resolve all references.

6.2. Interfaces for libglib-2.0

Table 6-1 defines the library name and shared object name for the libglib-2.0 library

6.3. Data Definitions for libglib-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libglib-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

#define G_STATIC_MUTEX_INIT	 \
	{ NULL, { { 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} } }
#define GPOINTER_TO_INT(p)	((glong) (p))
#define GLONG_TO_BE(val)	((glong) GINT64_TO_BE (val))
#define GLONG_TO_LE(val)	((glong) GINT64_TO_LE (val))
#define GINT_TO_POINTER(i)	((gpointer) (glong) (i))
#define GUINT_TO_POINTER(u)	((gpointer) (gulong) (u))
#define GPOINTER_TO_UINT(p)	((gulong) (p))
#define GULONG_TO_BE(val)	((gulong) GUINT64_TO_BE (val))
#define GULONG_TO_LE(val)	((gulong) GUINT64_TO_LE (val))
#define G_GINT64_CONSTANT(val)	(G_GNUC_EXTENSION (val ##L))
#define G_VA_COPY_AS_ARRAY	1
#define GLIB_LSB_PADDING_SIZE	40
#define GLIB_LSB_DATA_SIZE	8
#define GLIB_SIZEOF_LONG	8
#define GLIB_SIZEOF_SIZE_T	8
#define GLIB_SIZEOF_VOID_P	8
#define G_BYTE_ORDER	G_LITTLE_ENDIAN
#define G_MAXSIZE	G_MAXULONG
#define G_GINT64_MODIFIER	"l"
#define G_GSIZE_MODIFIER	"l"
#define G_GINT64_FORMAT	"li"
#define G_GSSIZE_FORMAT	"li"
#define G_GSIZE_FORMAT	"lu"
#define G_GUINT64_FORMAT	"lu"

typedef long int gssize;
typedef long int gint64;
typedef unsigned long int guint64;

typedef unsigned long int gsize;

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.4. Interfaces for libgobject-2.0

Table 6-2 defines the library name and shared object name for the libgobject-2.0 library

6.5. Data Definitions for libgobject-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libgobject-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.6. Interfaces for libgmodule-2.0

Table 6-3 defines the library name and shared object name for the libgmodule-2.0 library

6.7. Data Definitions for libgmodule-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libgmodule-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.8. Interfaces for libgthread-2.0

Table 6-4 defines the library name and shared object name for the libgthread-2.0 library

6.9. Interfaces for libatk-1.0

Table 6-5 defines the library name and shared object name for the libatk-1.0 library

6.10. Data Definitions for libatk-1.0

This section defines global identifiers and their values that are associated with interfaces contained in libatk-1.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.11. Interfaces for libpango-1.0

Table 6-6 defines the library name and shared object name for the libpango-1.0 library

6.12. Data Definitions for libpango-1.0

This section defines global identifiers and their values that are associated with interfaces contained in libpango-1.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.13. Interfaces for libpangoxft-1.0

Table 6-7 defines the library name and shared object name for the libpangoxft-1.0 library

6.14. Data Definitions for libpangoxft-1.0

This section defines global identifiers and their values that are associated with interfaces contained in libpangoxft-1.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.15. Interfaces for libpangoft2-1.0

Table 6-8 defines the library name and shared object name for the libpangoft2-1.0 library

6.16. Data Definitions for libpangoft2-1.0

This section defines global identifiers and their values that are associated with interfaces contained in libpangoft2-1.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.17. Interfaces for libgdk_pixbuf-2.0

Table 6-9 defines the library name and shared object name for the libgdk_pixbuf-2.0 library

6.18. Data Definitions for libgdk_pixbuf-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libgdk_pixbuf-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.19. Interfaces for libgdk_pixbuf_xlib-2.0

Table 6-10 defines the library name and shared object name for the libgdk_pixbuf_xlib-2.0 library

6.20. Data Definitions for libgdk_pixbuf_xlib-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libgdk_pixbuf_xlib-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.21. Interfaces for libgdk-x11-2.0

Table 6-11 defines the library name and shared object name for the libgdk-x11-2.0 library

6.22. Data Definitions for libgdk-x11-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libgdk-x11-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

6.23. Interfaces for libgtk-x11-2.0

Table 6-12 defines the library name and shared object name for the libgtk-x11-2.0 library

6.24. Data Definitions for libgtk-x11-2.0

This section defines global identifiers and their values that are associated with interfaces contained in libgtk-x11-2.0. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content. Where an interface is defined as requiring a particular system header file all of the data definitions for that system header file presented here shall be in effect.

This section gives data definitions to promote binary application portability, not to repeat source interface definitions available elsewhere. System providers and application developers should use this ABI to supplement - not to replace - source interface definition specifications.

This specification uses the ISO C (1999) C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

/*
 * This header is architecture neutral
 * Please refer to the generic specification for details
 */

7.1. Introduction

An conforming implementation shall support the following Qt libraries which provide interfaces for creating rich user applications, either graphical or console.

There are three main parts to the definition of each of these libraries.

The "Interfaces" section defines the required library name and version, and the required public symbols (interfaces and global data), as well as symbol versions, if any.

The "Interface Definitions" section provides complete or partial definitions of certain interfaces where either this specification is the source specification, or where there are variations from the source specification. If an interface definition requires one or more header files, one of those headers shall include the function prototype for the interface.

For source definitions of interfaces which include a reference to a header file, the contents of such header files form a part of the specification. The "Data Definitions" section provides the binary-level details for the header files from the source specifications, such as values for macros and enumerated types, as well as structure layouts, sizes and padding, etc. These data definitions, although presented in the form of header files for convenience, should not be taken a representing complete header files, as they are a supplement to the source specifications. Application developers should follow the guidelines of the source specifications when determining which header files need to be included to completely resolve all references.

7.2. Interfaces for libQtCore

Table 7-1 defines the library name and shared object name for the libQtCore library

The behavior of the interfaces in this library is specified by the following specifications: