| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the following macros and functions: GI_MAJOR_VERSION, GI_MICRO_VERSION,
GI_MINOR_VERSION, GI_CHECK_VERSION, gi_get_major_version,gi_get_micro_version,
gi_get_minor_version.
Since we share a prefix with glib we have to namespace these by using the gi_
prefix. g_gi would also work but we already export symbols with gi_ like
gi_cclosure_marshal_generic(), gi_type_tag_get_ffi_type() and
gi_type_info_extract_ffi_return_value(), so let's not add another naming scheme.
|
|
|
|
| |
This reverts commit 86b42e633c7679d97e7844ecec4c7783c6aedff0.
|
|
|
|
| |
It's part of autoconf-archive and lets us drop the acinclude.m4
|
|
|
|
|
|
| |
glib did the same thing this cycle, see
https://gitlab.gnome.org/GNOME/glib/merge_requests/196
for details
|
|
|
|
|
|
|
|
|
|
| |
This was the de facto behavior, and is already relied upon. If
gir-dir-prefix is specified, the gir dir will rely on the more generic
${prefix} location.
Also, avoid expanding the path unless necessary in the autotools build.
https://gitlab.gnome.org/GNOME/gobject-introspection/issues/236
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some .gir files such as GLib-2.0.gir are arch related which contain such
as lengths of pointers that they are different for 64 and 32 bit target.
It causes install file conflicts for multilib when intall
gobject-introspection and lib32-gobject-introspection both.
Add configure option 'with-gir-dir-prefix' for autotools to make .gir
could be installed to a configured path such as ${libdir}. And update
girdir in .pc files as well.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In order to generate HTML output that DevDocs can easily scrape and
display, we add a new output format to g-ir-doc-tool (--format=devdocs).
It works similarly to the Mallard output format, but generates very simple
HTML instead. We add a new set of Mako templates to generate this output.
|
|
|
|
| |
This lets us enable -Wdeprecated-declarations
|
|
|
|
|
| |
The ffi decls were added in cbdd9ee09e367e4dd to work around broken
ffi headers. Let's assume this is fixed now.
|
|
|
|
|
|
|
| |
In case the surrounding code handles missing cases break, otherwise add
a g_assert_not_reached().
The generated parser code triggers this as well, so disable it there only.
|
|
|
|
| |
hashv is unsigned, no need to check if >= 0
|
|
|
|
| |
and fix a missplaced break
|
|
|
|
|
| |
Except for the generated lexer code which triggers it with the
version of flex used in our CI.
|
| |
|
|
|
|
|
|
|
|
| |
Where it's easy add dummy args to match the cast; where the target is a subset just
prevent the warning with a cast to void*.
Provide a real copy function for the boxed type code in regress_foo.
This code is never executed afaics, but why not.
|
|
|
|
| |
And use G_GNUC_PRINTF for the suggested function.
|
| |
|
| |
|
|
|
|
|
| |
Except for the Python module because nothing in the CPython API is marked const
and we'd have to cast everywhere.
|
|
|
|
|
|
|
|
|
| |
* This adds a new dependency on autoconf-archive.
* Pass WARN_CFLAGS/WARN_LDFLAGS/WARN_SCANNERFLAGS to everything we control the source of
* Disables all warning flags which make the build error out for now, we'll re-enable them
in followup commits.
* AX_COMPILER_FLAGS is used with the release flag always on so we don't get
-Werror by default.
|
| |
|
|
|
|
|
| |
.pyd doesn't work with Python 3 on Windows, ask Python for what file extension
it expects instead of hardcoding it.
|
|
|
|
|
|
|
|
|
|
| |
We now have Meson build files which can handle builds using Visual
Studio now, so we should focus maintenance efforts on the build system
for Visual Studio on Meson.
This will also allow build options to be more flexible, and has the
advantage of being able to build directly out of a GIT checkout, without
needing to generate source dist tarballs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version file is generated at build time and stored as _version.py.
To support running uninstalled tools, a fallback version is included as
well. Example output of `--version` option:
```
$ for t in g-ir-{annotation-tool,scanner,doc-tool}; do $t --version; done
g-ir-annotation-tool 1.57.1
g-ir-scanner 1.57.1
g-ir-doc-tool 1.57.1
```
|
| |
|
| |
|
|
|
|
|
|
| |
autoreconf
See #120.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=792714
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... in the projects for now, the NMake Makefiles for the introspection files
(.gir/.typelib) need to be updated as well, but that needs to be done a bit
later.
This is done by updating the autotools scripts, so that the Visual Studio
2010 projects are copied and the items are updated as necessary.
Note that since the format of the platform toolset changed for Visual Studio
2017, a custom platform toolset string is allowed and used if specified,
otherwise the platform toolset string is generated as it was before.
|