| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This is what https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting suggests.
|
| |
|
| |
|
| |
|
|
|
|
| |
Patch taken from #74 (by Yeti)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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 should address flaky builds on vs2017-x64-meson.
|
| |
|
|
|
|
|
|
| |
API from gobject/gvaluecollector.h is not intended for introspected use.
Skip it when scanning headers. This effectively hides the definition of
GTypeCValue and VALUE_COLLECT_FORMAT_MAX_LENGTH constant.
|
| |
|
|
|
|
|
|
|
| |
Add option 'gir-dir-prefix' for meson to make the installation path of
.gir files could be configured which has been done for autoconf.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
|
| |
|
|
|
|
|
| |
Some structs are missing for me when running update-glib-annotations.
I've kept them as is and just included theannotation updates.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
meson: Add a "python" option to make the python to build against configurable
See merge request GNOME/gobject-introspection!50
|
| |
| |
| |
| |
| |
| |
| |
| | |
This allows us to build with Python 2 and run tests with it.
This requires the new "python" meson module which was added in 0.46.0 so
bump the required meson version (glib needs a newer one anyway).
Also fixes a small test error under Python 2.
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
Always use gobject-introspection-1.0 we have just built,
when running g-ir-scanner for girepository.
|
| |
|
|
|
|
| |
To make it build using libintl as a subproject on Linux.
|
| |
|
| |
|
|
|
|
| |
To make it build using libffi as a subproject on Linux.
|
|
|
|
|
|
|
|
|
|
|
| |
This ensures stability in the output, because the underlying
implementation uses readdir() and the output will depend on the
filesystem.
This also works around a bug where g-ir-scanner's source scanner was
#include-ing gmarshal.h before any other header which resulted in all
marshaling symbols to be skipped from the introspection because of
syntax errors.
|
|
|
|
|
|
| |
Otherwise we will see the fallback annotations provided in glib-2.0.c
etc and use them instead of the up-to-date annotations in glib's
source code.
|
|
|
|
|
| |
This is a hack for use by people who use a different subproject
directory than the default.
|
|
|
|
|
|
| |
When building from scratch on Windows using subprojects, we have neither
pkg-config nor any system libraries so we need to link to gio/glib/etc
manually.
|
|
|
|
| |
Signed-off-by: Nirbheek Chauhan <nirbheek@centricular.com>
|
|
|
|
|
|
|
| |
Both the source and the build dir are needed because some files are
read from the source and others are read after they are built.
Signed-off-by: Nirbheek Chauhan <nirbheek@centricular.com>
|
|
|
|
|
|
| |
Otherwise it won't run on Windows because it doesn't have a .py suffix
and it isn't an executable. Meson should probably detect this case and
automatically insert python3.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When building with Meson, we cannot set environment variables while
running custom targets and our builddir layout is different from
Autotools anyway.
Now g-ir-scanner and friends can autodetect when they're being run
uninstalled by Meson and will find _giscanner.so and the giscanner
python files in the build directory. This is very similar to what
gdbus-codegen uses in glib/gio.
Same for girepository/gdump.c.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous build files had a bunch of problems:
1. It assumed that glib would only be sourced via pkg-config
2. It was using the system gobject-introspection-1.0.pc file while
building GIRepository-1.0.gir
3. It wasn't ignoring the *-autocleanup.h headers properly
Now you can build glib as a subproject and generate girs against the
in-tree sources. This also yields more accurate girs because they
document platform-specific features that are actually enabled in
the glib build we are linking against.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 96c2e06aa661d37ad1cdf31825bbb921125357ae.
|
|
|
|
| |
Re-sync with GLib as of commit a4fc4c1e6eb57b10e2b60f522d11fd2c256dee31.
|
| |
|
| |
|
| |
|
| |
|