summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update GLib introspection datawip/smcv/testbuildRico Tzschichholz2023-01-303-106/+138
| | | | Use GLib commit f499e37979c09409d553a49562c6a0a9a65267af
* Update GLib introspection dataSebastian Dröge2023-01-302-25/+83
| | | | This is based on GLib ce876ab28bb81ac0b1c313223284de722d8208a1.
* Fix gir build when using subprojects' dependenciesAndoni Morales Alastruey2023-01-273-0/+16
| | | | | | | | https://github.com/mesonbuild/meson/pull/10275 introduced support in meson to use uninstalled .pc files in the meson-uninstalled directory to resolve dependencies built with subprojects. Replicate the same solution while all the custom_target are migrated to gnome.generate_dir
* Post-release version bump to 1.75.5Emmanuele Bassi2023-01-091-1/+1
|
* Release GObject-introspection 1.75.41.75.4Emmanuele Bassi2023-01-092-2/+7
|
* build: Remove subproject fallbackEmmanuele Bassi2023-01-091-14/+8
| | | | We don't need it any more.
* build: Override required GLib versionEmmanuele Bassi2023-01-091-2/+3
| | | | We passed GLib's own version, so we need to reset the requirement.
* Post-release version bump to 1.75.3Emmanuele Bassi2023-01-091-1/+1
|
* Release gobject-introspection 1.75.21.75.2Emmanuele Bassi2023-01-092-1/+11
|
* Update version to 1.75.1Emmanuele Bassi2023-01-081-1/+1
|
* tests: Use the appropriate assertion methodEmmanuele Bassi2023-01-081-53/+55
| | | | | | - assertEqual(value, None) → assertIsNone(value) - assertTrue(value is not None) → assertIsNotNone(value) - assertTrue(isinstance(value, Type)) → assertIsInstance(value, Type)
* Use the pointer attribute in libgirepositoryEmmanuele Bassi2023-01-084-20/+75
| | | | | | The "disguised" attribute is there only for backward compatibility; we use the "pointer" attribute as the authoritative way to indicate a typedef to a struct pointer.
* Split disguised attribute into twoEmmanuele Bassi2023-01-0811-20/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The disguised attribute started off as a way to indicate a typedef to a structure pointer, e.g. typedef struct Foo* FooPtr; Over the years, though, it started to include opaque structure types, e.g. typedef struct _FooObject FooObject; typedef struct _FooObjectClass FooObjectClass; This has led to issues in language bindings, code generators, and documentation generators, which now have issues when dealing with both pointer aliases and opaque types. An initial attempt at fixing this mess in commit f606183a ended up breaking Vala, and had to be reverted. To avoid breaking existing users we can follow a similar approach to the allow-none/nullable/optional solution: 1. introduce a new pair of attributes: "pointer" and "opaque" 2. deprecate the "disguised" attribute The "pointer" attribute covers the case of pointer types. The "opaque" attribute covers the case of opaque structured types. See also: https://gitlab.gnome.org/GNOME/vala/-/issues/735 Fixes: #101
* Revert "scanner: don't accept invalid symbols in binary expressions"Emmanuele Bassi2023-01-087-41/+84
| | | | This reverts commit b37f24b7e27a77c398f41cc331608aff806f0d42.
* GIMarshallingTests: Free and copy GStrv instancesMarco Trevisan (Treviño)2023-01-081-0/+2
| | | | | A GIMarshallingTestsBoxedStruct includes a GStrv, but we don't copy or free it properly.
* Document the newly added attributesEmmanuele Bassi2023-01-082-0/+16
| | | | | Add the (copy-func) and (free-func) annotations to the documentation, and the copy-function and free-function attributes to the GIR schema.
* test: Add regression test for the new tagsEmmanuele Bassi2023-01-086-229/+260
|
* Add copy and free function annotations for POD typesEmmanuele Bassi2023-01-0814-15/+287
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Plain Old Data (POD) types with or without a representation in the GType type system can still have a copy and/or a free function. We should allow annotating these types with their corresponding functions for copying their data into a new instance, and freeing their data. From a language bindings perspective, POD types should have a boxed GType wrapper around them, so they can use the generic GBoxed API to copy and free instances; from a documentation perspective, though, it'd be good to have a way to match a structured type, like a struct or a union, with its copy and free functions. In order to do that, we add two new header block annotations: - (copy-func function_name) - (free-func function_name) These annotations work exactly like ref-func and unref-func for typed instances: /** * GdkRGBA: (copy-func gdk_rgba_copy) * (free-func gdk_rgba_free) * @red: ... * @green: ... * @blue: ... * @alpha: ... * * ... */ The function is stored in the GIR data as two new attributes for the `<record>` and `<union>` elements: <record name="RGBA" c:type="GdkRGBA" copy-function="gdk_rgba_copy" free-function="gdk_rgba_free" glib:type-name="GdkRGBA" glib:get-type="gdk_rgba_get_type" c:symbol-prefix="gdk_rgba"> The annotations are not mandatory. See: #14
* Open g-i 1.75 developmentEmmanuele Bassi2023-01-081-0/+14
|
* Add `default-value` annotationEmmanuele Bassi2023-01-085-7/+37
| | | | | | | An escape hatch to specify a freeform string for the default value of a property. Fixes: #4
* Skip default-value for non-transformable propertiesEmmanuele Bassi2023-01-083-45/+34
| | | | | | | If we can't transform a property default value to string, we are not going to add a default-value attribute to the GIR. This is necessary because non-transformable values may not always be pointers, so we cannot default to "NULL".
* Add an optional attribute for the property default valueEmmanuele Bassi2023-01-086-25/+75
| | | | | | | | | The default-value attribute for a property element is fundamentally meant for documentation generators. We only care about the GIR data, as the conversion from the default value to a string is lossy by definition, and may very well not roundtrip.
* Dump the default value of object propertiesEmmanuele Bassi2023-01-081-2/+45
| | | | | | We use g_param_spec_get_default_value() to get the default GValue of a GParamSpec, and then we serialize it into a string according to the value's own contents and type.
* Remove function "FT_Library_Version"badcel2023-01-081-7/+0
| | | | The function is not usable for language bindings as no shared library name is defined in the gir file and the parameters do not match upstream function signature.
* Update GLib introspection dataEmmanuele Bassi2023-01-083-50/+509
| | | | Use GLib commit ec3b1bfc45216850c1a861055ad2fd9d9906813a (tag: 2.75.2)
* scanner: don't accept invalid symbols in binary expressionsLubomir Rintel2023-01-087-84/+41
| | | | | | | | | | | | | | | | | | | | | The rules for binary expressions were entirely oblivious to the type of the operand symbols and assumed they're integer constants. This is very unfortunate, since it caused all sort of nonsense to end up getting accepted. One such example is the following define from NetworkManager's libnm: #define NM_SETTING_PARAM_SECRET (1 << (2 + G_PARAM_USER_SHIFT)) As G_PARAM_USER_SHIFT is unknown, it was parsed as an invalid symbol. The addition didn't care, treated it as: #define NM_SETTING_PARAM_SECRET (1 << (2 + 0)) Let's just ensure we get CSYMBOL_TYPE_CONST only when both operands actually have const_int_set. Otherwise just create CSYMBOL_TYPE_INVALID. That will cause the symbol to be dropped on the floor eventually, but that's probably much better than a having an invalid value.
* tests/scanner: add some tests for #definesLubomir Rintel2023-01-088-239/+337
| | | | | | | | Add one expanding to an expression we can't get a constant value from and another one for which we can. Note that the bad on one currently does evaluate, and it does so to a bad value. A separate commit with a diff to test suite will address that.
* Track the main branch of GLib as a subprojectEmmanuele Bassi2023-01-081-1/+1
| | | | GObject-introspection is meant to match GLib.
* Bump the project version to 1.75.0Emmanuele Bassi2023-01-081-1/+1
| | | | New cycle, new version number.
* build: Add missing header and symbolsEmmanuele Bassi2023-01-081-0/+3
| | | | | | | | | | | Now that GLib has separate version annotation macros, we need to define GOBJECT_COMPILATION and parse gobject-visibility.h when generating the introspection data for GLib. This MR also requires: - GNOME/glib!3184 - GNOME/glib!3185
* build: Add missing GMODULE_COMPILATION symbolEmmanuele Bassi2023-01-081-0/+1
| | | | | We need to define GMODULE_COMPILATION when building the introspection data for GModule.
* build: Drop wrap files for GLib dependenciesEmmanuele Bassi2023-01-085-28/+12
| | | | We don't need wrap files for things we get from GLib or from the system.
* scanner: Ignore unused typing importEmmanuele Bassi2023-01-081-2/+2
| | | | | Ignore the typing import so that flake8 doesn't complain, and mypy keeps working.
* gimarshallingtests: Add Structured Union types, unions with struct fieldsMarco Trevisan (Treviño)2022-11-212-0/+229
| | | | | | This allows to perform more introspection tests in gjs and other implementations when it comes to set/get fields or "cast" an union member to the main union type
* GIMarshallingTests: Add tests for caller allocated fixed size arraysMarco Trevisan (Treviño)2022-11-212-0/+36
| | | | | | | Such kind of arrays can be easily be allocated as we know the size of each array element. See: https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/806
* Update glib introspection dataRico Tzschichholz2022-11-132-17/+6
| | | | This is based on f64f88baaeaca277687e6231b3cea6d14a26996b
* Update glib introspection dataSebastian Dröge2022-11-033-55/+596
| | | | This is based on 201c920cbd0b816f4e19b52c1b28746935fdcb00.
* Update glib introspection dataSebastian Dröge2022-10-213-37/+76
| | | | Based on 86430a27d26b9b72b02ff0b81eeaa5df0525646c.
* Fix typo in async scope descriptionbadcel2022-10-061-2/+2
|
* Add missing (void) arguments to comply with -Wstrict-prototypesMarco Trevisan (Treviño)2022-10-062-2/+2
|
* cmph: Do not set debug variables if debug is not setMarco Trevisan (Treviño)2022-10-061-1/+3
| | | | Fixes clang builds
* Post-release version bump to 1.74.1Emmanuele Bassi2022-09-171-1/+1
|
* Release GObject-introspection 1.74.01.74.0Emmanuele Bassi2022-09-172-1/+6
|
* Update GLib annotationsEmmanuele Bassi2022-09-173-9/+9
| | | | GLib commit: 2.74.0
* Post-release version bump to 1.73.2Emmanuele Bassi2022-09-031-1/+1
|
* Release gobject-introspection 1.73.11.73.1Emmanuele Bassi2022-09-031-0/+12
|
* giscanner: undef "GLIB_VERSION_{MAX_ALLOWED,MIN_REQUIRED}" macros in ↵Thomas Haller2022-09-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | generated C file When g-ir-scanner is used by another project, than that project might have the GLIB_VERSION_* macros defined. This is useful to ensure that only intended glib API is used. The project might then also pass the CFLAGS to g-ir-scanner, without filtering those defines out. This can lead to compiler warnings. For example, NetworkManager sets the version macros to GLIB_VERSION_2_40 and thus gets these warnings /NetworkManager/tmp-introspect66917zc4/NM-1.0.c: In function ‘dump_object_type’: /NetworkManager/tmp-introspect66917zc4/NM-1.0.c:252:13: warning: Not available before 2.70 252 | if (G_TYPE_IS_FINAL (type)) | ^~~~~~~~~~~~~~~~~ /NetworkManager/tmp-introspect66917zc4/NM-1.0.c: In function ‘dump_fundamental_type’: /NetworkManager/tmp-introspect66917zc4/NM-1.0.c:370:13: warning: Not available before 2.70 370 | if (G_TYPE_IS_FINAL (type)) | ^~~~~~~~~~~~~~~~~ But these warnings are not correct. The installed g-ir-scanner knows for which glib version to generate code. Undefine the macros to avoid the warning.
* Update GLib annotationsEmmanuele Bassi2022-09-023-54/+92
| | | | GLib commit: 2.73.3-44-g66c4e35e2
* Require C99Emmanuele Bassi2022-08-311-1/+1
| | | | | GLib has been requiring a C99 toolchain for a while, now. It makes no sense to have gobject-introspection depend on C89.
* doctool: prepend the emitting object for GJS signal callbacksAndy Holmes2022-08-314-3/+16
|
View Lorry Controller Status