| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
Newer meson warns that option names can't start with "cross_", so
we have to prefix them:
"Option uses prefix "cross_", which is reserved for Meson. This will become an error in the future."
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids compilation erroring out on C4819 (Unicode handling issue in the
Visual Studio compiler), notably when running on Chinese, Japanese and Korean
(CJK) locales.
This also applies -utf-8 into the cflags passed into the various g-ir-scanner
command lines that are used to generate the *.gir files, where -utf-8 is
available, so that we don't get flooded with C4819 warnings during the
build, and therefore avoid potential mishaps, as C4819 is a real warning that
warngs us the code may be incorrectly built.
|
| |
|
|
|
|
|
|
|
|
|
| |
See here:
https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/64
Particularly, options are renamed to make it more readable and clear.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
introspection-data and pkgconfig-sysroot-path options
With the first option, gobject-introspection tools (g-ir-doc-tool and g-ir-scanner)
that are already installed in the host system will be used for building the source tree.
With the second option, g-ir-scanner will be instructed to use an executable
wrapper to run binaries it's producing, and g-ir-compiler will be run
through the same wrapper (host system's g-ir-compiler cannot be used because
it's producing architecture-specific output).
With the third option, giscanner will be instructed to use a special ldd
command instead of system's ldd (which does not work when the binary to inspect
is compiled for a different architecture).
With the fourth option, it is possible to disable building of introspection data
(.gir and .typelib files), which may be difficult or impossible in cross-compilation
environments, because of lack of emulation (or native hardware) for the target architecture
on which the target binaries can be run.
With the fifth option, paths returned by pkg-config are prefixed with the sysroot
path (which is the destination path for cross-compiled items on the system where
cross-compilation happens).
These options are useful when cross-compiling for a different target architecture.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/300.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The cairo MSVC build produces a cairo-gobject.dll unlike the
libcairo-gobject-2.dll with autotools.
While one can pass the right DLL name through the cairo_libname option,
having a better default can't hurt.
|
| |
|
|
|
|
| |
host_machine.system() returns "windows" on Windows
|
|
|
|
| |
Less noisy build
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The newly added GTypes in glib!481 result in g-i generating an enum type
in GLib-2.0 and a GType based one in GObject-2.0.
This makes problems for the dlang bindings (see #267) so skip them for now.
Ideally we should include it in GLib-2.0 like we do with glib-types.h.
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|