| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
The cairo dependency fallback code is copied from pygobject. I assume that
will work for msvc users (cairo is disabled by default anyway)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Otherwise when you set CC=clang then distuils will still use gcc for linking.
While it seems we don't invoke the link command atm this shouldn't hurt.
The upstream customize_compiler() does the same thing on macOS and there is a bug
for enabling it everywhere: https://bugs.python.org/issue24935
|
| |
|
|
|
|
|
|
|
| |
The position attributes on a <doc> element are not mandatory, so we
should have some fallback value if they are missing.
Fixes: #252
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Only use flags provided by env vars from the user and never from the
Python sysconfig. The sysconfig values depend on the way Python was built,
might conflict when using g-i with a different compiler and can't be controlled
by the g-i user.
|
|
|
|
|
|
|
|
| |
So we have more control over it.
This also removes all macOS specific bits from it because I'm not sure if they are
needed and they depend in internal API. This means this change can cause functional
changes. Please report if you hit any!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
No functional changes intended.
Tests check that:
* Compiler is obtained from CC.
* cc is used as the default compiler.
Currently not true as a Python build time compiler is used as the default.
* Preprocessor is obtained from CC when CPP is unspecified by adding -E.
* Preprocessor is obtained from CPP.
* cpp is used as the default preprocessor.
Currently not true as Python build time preprocessor is used as the default.
* Shell word splitting rules are used to split CC.
* Shell word splitting rules are used to split CPP.
* Deprecation warnings are disabled during compilation.
* Preprocessing step includes CPPFLAGS.
* Compilation step includes both CFLAGS and CPPFLAGS, in that order.
* Macros from CFLAGS are defined only once.
Currently not true as they are defined twice.
* Flags that would retain macros after preprocessing step are filtered out.
Currently only partially true as they aren't filtered out from CPPFLAGS.
* Preprocessing step includes flag that preserves comments.
* Preprocessing step includes current working directory.
* Complete preprocessing command doesn't contain anything unexpected.
Currently not true as Python build time CPPFLAGS are included as well.
* Complete build command doesn't contain anything unexpected.
Currently not true as Python build time CFLAGS and CPPFLAGS are included as well.
|
| |
|
|
|
|
|
|
|
|
|
| |
With !45 special casing of bool in the lexer was removed which previously allowed the usage of
bool without including stdbool.h. This breaks scanning of graphene headers
which guarded the stdbool include with __GI_SCANNER__ (I haven't figured out why).
Add back the special handling for bool in the lexer and also map it to gboolean like
_Bool as if stdbool.h was included.
|
|
|
|
|
| |
The headerid extension no longer exists in 3.x. Use the toc extension instead.
The toc_depth option was only added in 3.x so still try headerid first.
|
|
|
|
|
|
|
|
| |
Manually add all the subproject build directories to PATH for running
the scanner tests.
I'm wondering if meson shouldn't do this for us based on the dependency
we pass to test(), but this will do for now.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Generating offsets test makes them quite hard to understand. The fact
that they parse C code with custom regular expressions don't help
either.
Replace offsets test with their generated form.
|
| |
|
|
|
|
| |
Patch taken from #74 (by Yeti)
|
|
|
|
| |
So we don't ignore any PYTHONPATH set by the user.
|
| |
|
|
|
|
|
|
|
|
| |
This enables various compiler warnings project wide and disables the triggered
ones for each library/executable. This should give us roughly the same behaviour
as with autotools.
Tested with gcc8 and clang7.
|
|
|
|
| |
Removes a warning on an unreplaced pattern.
|
|
|
|
|
| |
The configure_file target has grown a `copy` argument to avoid using an
empty configuration_data object since Meson 0.47.
|
|
|
|
|
| |
We should probably require a newer stable release, but this should be
enough to remove the warnings.
|
|
|
|
|
| |
Like we currently do with autotools.
See https://github.com/mesonbuild/meson/issues/4117
|
|
|
|
|
|
| |
This requires a code change in codegen.py to support the case whre output files
are not installed in the working directory. Instead of using the output
path for the header include use the relative path to the output source file.
|
|
|
|
| |
Not sure if they are used, but we should try to do the same thing as autotools for starters
|
|
|
|
| |
Noticed while comparing meson and autotools output
|
|
|
|
| |
Noticed when comparing meson and autotools build results
|
|
|
|
|
| |
Add a simple test using the docwriter so we trigger the docwriter related
Python imports.
|
|
|
|
|
|
|
|
|
|
| |
Clean up the code and make it work with meson. Assume a fixed build dir
to make it less magic and so we can give better error messages.
This also removes all the include path logic because since c93dafe97e70
it no longer parses headers anyway and it wasn't doing anything with it.
Also tested on Windows.
|
|
|
|
|
|
|
|
|
|
| |
When using `GI_SCANNER_DEBUG=save-temps`, the temporary input file
to be preprocessed and temporary output file that is result of this
preprocessing are retained for debugging purposes. Use together with
`-v` option to actually determine names of those temporary files.
This should make it easier to determine the source of parsing errors,
like those described in the #247.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes #96
GITypeInfo is a GIBaseInfo so calling g_base_info_get_name() on it should do something
sensible.
g_base_info_get_name() has always been documented to return NULL in case no name
is available so return that instead.
|
|
|
|
| |
See #66
|
|
|
|
|
|
| |
section
Move them to where the type is documented.
|
|
|
|
| |
It's easy to break non-srcdir builds so make sure we catch it in CI
|
|\
| |
| |
| |
| | |
docs: Field offsets are in the units of bytes
See merge request GNOME/gobject-introspection!97
|
|/ |
|