summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release GObject Introspection 1.73.01.73.0Emmanuele Bassi2022-07-131-0/+8
|
* build: Remove a version check that is always trueEmmanuele Bassi2022-07-131-4/+1
| | | | We require Meson 0.60, to match newer GLib.
* build: Add run_command() argumentEmmanuele Bassi2022-07-133-10/+10
| | | | The `check` argument to `run_command()` is now mandatory.
* ci: Update MSYS2 testEmmanuele Bassi2022-07-131-8/+16
| | | | | | - Install pcre2, as it's a new GLib dependency. - Do not use CFLAGS to inject -Werror - Use idiomatic Meson subcommands
* Always require the latest GLibEmmanuele Bassi2022-07-131-3/+1
| | | | | GLib 2.58 has long since been released. We should always match GLib's version, since we update the introspection data regularly.
* Update GLib introspection dataEmmanuele Bassi2022-07-132-3/+3
| | | | Rebased up to 2.73.2.
* gir: Update introspection data to GLib 2.73.1Marco Trevisan (Treviño)2022-06-283-54/+526
| | | | Based on https://gitlab.gnome.org/GNOME/glib/-/commit/113d7263
* Add FcConfig to the rump fontconfig girMatthias Clasen2022-06-111-0/+1
| | | | | | | This 10 line gir file was good enough for the past 12 years, but now I want to have pango api with FcConfig arguments appear in the docs, and the way to that leads through the gir nowadays.
* ci: Temporarily disable tests on MSVCEmmanuele Bassi2022-06-111-1/+1
| | | | We need to unblock the CI pipeline, in order to fix them.
* Update the zlib wrap fileEmmanuele Bassi2022-06-111-5/+12
| | | | The original one was so old Meson didn't recognise it as a wrap file.
* ci: Install zlib in the minimal imageEmmanuele Bassi2022-06-111-0/+1
|
* ci: Update the version of Meson for the Windows buildsEmmanuele Bassi2022-06-112-2/+2
|
* ci: Use the latest imagesEmmanuele Bassi2022-06-111-2/+2
|
* ci: Bump the image versionEmmanuele Bassi2022-06-112-2/+2
|
* ci: Update to Fedora 36Emmanuele Bassi2022-06-112-2/+2
| | | | | Fedora 34 is EOL, and by the time we release GNOME 43, Fedora 35 will be close to EOL too.
* ci: Bump up the version of MesonEmmanuele Bassi2022-06-112-2/+2
|
* Update the required version of MesonEmmanuele Bassi2022-06-111-1/+1
| | | | GLib bumped its own dependency to Meson 0.60.
* Update to 1.73.0Emmanuele Bassi2022-06-111-1/+1
|
* docs: Update documentation links in the GIR schemaTestingPlant2022-04-291-2/+2
|
* Update GLib introspection dataSebastian Dröge2022-04-293-9/+54
| | | | This is based on 0c6a1af9d616e110b4610d5a6a992d02ed1a5c21
* examples: fix typo in error messageReuben Thomas2022-04-161-1/+1
| | | | | In glib-print.c example, make the error message refer to the same function (GLib.assertion_message) as the code.
* gi: fix build of pango from subprojectsAndoni Morales Alastruey2022-04-111-16/+22
| | | | | | | | | Projects like pango depending on fontconfig-2.0.gir or any other gir provided by gobject-introspection in its sources directory need to have these gir's available in the build directory, where the rest of generated girs are created so they are found when using gobject-introspection dependency.
* gir: fix build as subprojectAndoni Morales Alastruey2022-04-051-11/+11
| | | | | | Fix sandbox violation using subproject variables added in https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2465 Use global source and build root directories
* gi[callable|type]info.c: Avoid MSVC C4098 warningsChun-wei Fan2022-03-282-4/+4
| | | | | | | | | We attempted to return a value in void-return-type functions in both gicallableinfo.c and gitypeinfo.c, so avoid that since that will trigger a C4098 warning on Visual Studio, which is considered an error if we are building against an installed version of GLib 2.68.x or later. This will fix builds against GLib-2.68.x and later on Visual Studio.
* giscanner: Support ISO varargs in function macrosPhilip Withnall2022-03-221-1/+22
| | | | | | This fixes support for macros like `g_message()` in GLib. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
* giscanner: Support function macros with zero argumentsPhilip Withnall2022-03-221-0/+10
| | | | | | | This fixes support for macros like `G_BREAKPOINT()` or `G_DEBUG_HERE()` in GLib. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
* Post-release version bump to 1.72.1Emmanuele Bassi2022-03-181-1/+1
|
* Release GObject-Introspection 1.72.01.72.0Emmanuele Bassi2022-03-182-1/+8
|
* Update GLib's introspection dataEmmanuele Bassi2022-03-184-229/+253
| | | | GLib 2.72.0 is now out.
* scanner: Check before accessing an optional fieldEmmanuele Bassi2022-03-181-1/+2
| | | | | | | | | It seems that optparse might just ignore storing options without a default. In this case, the `--compiler` option should be initialised to `None`, but instead it just gets ignored. Without the `hasattr()` check, updating the introspection data for GLib fails with a Python backtrace.
* Update glib introspection dataSebastian Dröge2022-02-201-3/+121
| | | | This is based on f61187428eaff51b5aae121df1615e02117ef44f.
* Clean up the Git ignore fileEmmanuele Bassi2022-02-171-151/+4
| | | | | We don't use Autotools, and we don't generate files inside the source directory any more.
* Rename the main development branchEmmanuele Bassi2022-02-174-13/+28
| | | | | The main development branch of GObject Introspection is now called "main", following the change in GLib and GTK.
* gitypeinfo: Add pointer-stuffing functions for GITypeTag storage typePhilip Chimento2022-02-162-20/+84
| | | | | | | | | | | | | | | | | | | | | This adds gi_type_tag_argument_from_hash_pointer() and gi_type_tag_hash_pointer_from_argument(). They do the same thing as the corresponding g_type_info_... functions, which are used to pack and unpack the correct field of a GIArgument into/from a data pointer in GHashTable or GList, regardless of machine architecture or endianness. These functions take a GITypeTag obtained from g_type_info_get_storage_type(), instead of a GITypeInfo pointer. (The storage type is the only piece of data that is actually used from the GITypeInfo structure.) It's intended for bindings using an argument cache, such as GJS and PyGObject, so that they don't have to store a whole 64-bit GITypeInfo pointer in their cache in many common cases, and can just store the 5-bit type tag instead. The original g_type_info_... functions are reimplemented in terms of the new g_type_tag... functions.
* Post-release version bump to 1.71.1Emmanuele Bassi2022-02-141-1/+1
|
* Release gobject-introspection 1.71.01.71.0Emmanuele Bassi2022-02-141-0/+19
|
* scannerparser.y: Include io.h on WindowsChun-wei Fan2022-02-131-0/+4
| | | | | We need it for close(), especially when unistd.h is not available, such as in the case of Visual Studio-style builds.
* bdz.c: Some cleanupsChun-wei Fan2022-02-131-9/+1
| | | | | | | | We can just update the for loop condition to be >0 for all builds, which is actually equivilant to >=1 as we are essentially comparing an unsigned 32-bit int, so that we don't need to worry about fixing the VS2012 bug invasively, as Visual Studio 2012 x64 is more sensitive about sizes of variables (e.g. pointer sizes in this case)
* brz.c: Consider _WIN64 for 64-bit pointers tooChun-wei Fan2022-02-131-8/+12
| | | | | | | | | | | The __ia64 and __x86_64__ macros are defined for GCC but not Visual Studio, but actually this code path should also be taken for Visual Studio when doing a 64-bit build (x86_64/x64 and aarch64/arm64, _WIN64 will be defined for these cases), since Windows is an LLP64 platform. This will avoid C4311/C4312 warnings on Visual Studio builds, which are often warnings of concern as we are dealing with pointers with differing sizes on 32-bit and 64-bit Windows builds.
* brz.c: Avoid C4715 warningsChun-wei Fan2022-02-131-1/+3
| | | | | | | | | Later GLib versions assume that warning C4715 is an error as we want ot be sure that functions that return a value do indeed return one by all means. Avoid this warning by adding a 'return 0' in brz_search_packed(), it might be pointless but does indeed avoid the warning.
* docs: Add missing versioned indicesEmmanuele Bassi2022-02-131-0/+16
| | | | | It's pointless, as docbook's style sheets do not work any more, but gtk-doc still warns about them.
* Rename argument in the declationEmmanuele Bassi2022-02-131-1/+1
| | | | It must match the argument in the definition and the documentation.
* docs: Add missing symbols to the sections fileEmmanuele Bassi2022-02-131-0/+19
|
* Use GI_TYPE_TAG_IS_BASICEmmanuele Bassi2022-02-134-6/+6
| | | | Now that we have it.
* Add GI_TYPE_TAG_IS_BASICEmmanuele Bassi2022-02-131-1/+33
| | | | | And deprecate G_TYPE_TAG_IS_BASIC. Let's avoid hijacking the G namespace any further.
* docs: Rename a field annotationEmmanuele Bassi2022-02-131-1/+1
|
* docs: Reformat a long descriptionEmmanuele Bassi2022-02-131-0/+4
|
* docs: Remove DocBook tagsEmmanuele Bassi2022-02-1318-246/+117
| | | | | We are still using gtk-doc, but gtk-doc uses Markdown these days, not DocBook.
* Use the proper private triglyphEmmanuele Bassi2022-02-134-5/+4
| | | | It's `/*< ... >*/`, not `/* <...> */`.
* girffi: Add gi_type_tag_extract_ffi_return_value()Philip Chimento2022-02-132-26/+62
| | | | | | | | | | | | | | | | This new API does the same thing as gi_type_info_extract_ffi_return_value, but takes a GITypeTag instead of GITypeInfo pointer, and additionally a GIInfoType if the GITypeTag is GI_TYPE_TAG_INTERFACE. (These pieces of data are the only things used from the GITypeInfo structure.) It's intended for bindings using an argument cache, such as GJS and PyGObject, so that they don't have to store a whole 64-bit GITypeInfo pointer in their cache in many common cases, and can just store the 5-bit type tag instead, or the 5-bit interface type in case of GI_TYPE_TAG_INTERFACE. The original gi_type_info_extract_ffi_return_value() is reimplemented in terms of the new gi_type_tag_extract_ffi_return_value().
View Lorry Controller Status