| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Bindings sometimes need to handle flags and enums separately, so
everything that is tested for enums should ideally be tested separately
for flags.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
| |
We already had a test for enums, but flags are not precisely the same,
so testing both can give bindings better coverage.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
giscanner: Fix section matching for documentation
Closes #350
See merge request GNOME/gobject-introspection!237
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
When writing documentation to the GIR files, GIR tries to match
classes with their matching SECTION: comment in the source code. Some codebases
use kebab-case or CamelCase for their section names, but GIR always expects
them to be flatcase or the matching will fail.
This commit converts all section names to flatcase (by removing "-" and
converting to lowercase) while they are being parsed, so that they are matched
properly later on.
Fixes #350.
|
|\
| |
| |
| |
| | |
giscanner: Add support for using clang-cl
See merge request GNOME/gobject-introspection!234
|
| |
| |
| |
| |
| | |
Let people know how building G-I and running g-ir-scanner with clang-cl and
friends is being supported, as this support is now added.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds quick support for using 'clang-cl' (CLang's emulation of the Visual
Studio compiler) to run giscanner.
This will still initialize things mostly in the MSVC fashion, except that it
will also check whether both 'CC' and 'CXX' envvars are set to
'clang-cl [args]', as per the way that Meson supports using 'clang-cl'.
Since we are using distutils to set up the compiler instance, when we enable
'clang-cl' support, we trick distutils that we have already initialized the
MSVCCompiler parameters as needed. We just leave out the compiler flags as
we don't really care about debug symbols nor optimization with the built
dumper binary, as it is gone as soon as the .gir file is generated.
This will build G-I successfully with all the tests passed.
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
website: Add section about property/method name conflicts
See merge request GNOME/gobject-introspection!232
|
| |
| |
| |
| |
| | |
This is a trap that C APIs can fall into, so it should be mentioned on
the "Writing Bindable APIs" page.
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Add missing nullable annotations to GObjectInfo
See merge request GNOME/gobject-introspection!225
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Add the notion of standalone doc sections.
See merge request GNOME/gobject-introspection!226
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Up to now, section annotations had to match a class or interface
name in order to be serialized in the gir.
With this commit, they now get serialized as docsection nodes,
for potential use by documentation tools.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
giscanner: parse block comments for members and fields
Closes #348
See merge request GNOME/gobject-introspection!230
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There was previously no mechanism for tagging enum members
and struct fields with Since tags (or other, eg deprecation tags).
While the customary place to add Since tags for these symbols
is inline in the parent symbol's documentation eg:
/**
* Foo:
*
* @FOO_BAR: some bar. Since X.Y
*/
And variations on that theme, implementing parsing for that scheme
would result in a pretty ambiguous grammar, especially if we also
want support for multiple tags.
Instead, the solution implemented here is to allow providing
documentation for individual members and fields through their
own separate block, as is done for virtual functions already.
Inline comments are still used, with a lower precedence.
Fixes #348
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
[Win32] Fix gi-dump-types.c to build on Windows
See merge request GNOME/gobject-introspection!218
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`g_win32_output_stream_new_from_fd()` is private in Gio.
It's normally not exported unless `GLIB_STATIC_COMPILATION` is effective.
PS. Why would i not be called `GIO_STATIC_COMPILATION` for Gio .c-files?
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
meson.build: Fix generating pkg-config files
See merge request GNOME/gobject-introspection!229
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
On Windows and Cygwin builds, we need to put the '.exe' for our entries
into the pkg-config files for 'g-ir-compiler' and 'g-ir-generate',
otherwise Meson will not be able to identify these programs correctly.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
gir: add a dependency for g-ir-compiler for building .girs
See merge request GNOME/gobject-introspection!228
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
meson inserts the dependency if the compiler is used directly, but
fails to do so if the compiler is run through a wrapper. This leads
to build race errors between building the compiler and using it.
Fix provided by Quentin Schulz <quentin.schulz@streamunlimited.com>
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
CI: add two jobs building a project using g-i with meson and autotools
Closes #341
See merge request GNOME/gobject-introspection!223
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
This tests that after installing the g-i tools a simple project using
them can be build with meson and autotools.
Fixes #341
|
| | |
| | |
| | |
| | | |
See !207
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Meson: Use pkgconfig generator
See merge request GNOME/gobject-introspection!207
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Don't override finding executables when using pre-built tools.
See merge request GNOME/gobject-introspection!212
|
| |\ \ \ \
| |/ / / /
|/| | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Rename option `gi_cross_use_{host -> prebuilt}_gi`
See merge request GNOME/gobject-introspection!211
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The old name used "host" according to Yocto's definition, but not
Meson's. The new name works for everyone.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
Remove old autoconf fallback code for the python tools.
See merge request GNOME/gobject-introspection!221
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Minor docs fixes
See merge request GNOME/gobject-introspection!220
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
There has been no backwards incompatible changes between DockBook 4.3
and 4.5 so there is no need to use both.
Ideally, we would switch to DocBook 5 but that will require more changes.
|
|/ / / / / |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
dumper: Fix missing symbols in LTO case or with overridden symbol visibility settings
Closes #280
See merge request GNOME/gobject-introspection!216
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
settings
In case a user had a combination of -fvisibility=hidden, -Wl,--as-needed, -flto, -O2
in the CFLAGS the linker would sometimes detect that all the referenced gtype functions
weren't actually used and throw them out with their providing libraries.
Instead of hoping that the user's CFLAGS don't mess without our symbol visibility just use
G_MODULE_EXPORT on the two symbols which reference all other gtype and gquark symbols.
This fixes errors such as:
Invalid GType function: 'gtk_accel_group_get_type'
Failed to find symbol 'gtk_accel_group_get_type'
during the g-ir-scanner execution.
Fixes #280
|
| | | | |
|