| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
MSVC Builds: Fix _giscanner projects
See merge request GNOME/gobject-introspection!21
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix the header name for GObject-2.0.gir, and do not include the
GLib-2.0.gir in Gio-2.0.gir, as it already includes GObject-2.0.gir
which in turn includes GLib-2.0.gir.
This makes these .gir files conform better to the ones produced by
the autotools/Meson builds.
|
| |
| |
| |
| |
| |
| | |
The scanner[lexer|parser] sources are now in giscanner/, not $(srcroot),
so we need to update the Visual Studio project files to make sure things
build properly.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently g-ir-scanner fails on macOS when invoked in --no-libtool mode
if the library it links to has not been installed into its destination
(which is likely to be the case). In libtool mode this issue does not
occur as DYLD_LIBRARY_PATH will get set by libtool in an appropriate
manner. This patch ensures DYLD_LIBRARY_PATH will get set.
This patch is also essential for meson and cmake to generate
gobject-introspection bindings.
More information can be found e.g. at
https://mail.gnome.org/archives/gtk-osx-users-list/2018-February/msg00000.html,
and the github repo that was produced subsequently at
https://github.com/wagavulin/gir-mac-sample.
|
| |
|
|
|
|
|
| |
Signed-off-by: Nirbheek Chauhan <nirbheek@centricular.com>
(cherry picked from commit 52a5c7eb4e63f45a9d982de81515bbf7e13e3fd5)
|
|
|
|
| |
(cherry picked from commit 695ed85afa9034a8d68a71572fa5450c428cd8be)
|
|
|
|
|
|
|
|
| |
Also disable automatic hyphenation in manual pages to prevent wrapping
long URLs. Ensures that URLs can be easily navigated by clicking on
them.
(cherry picked from commit 6a8e1b8ad69e5ec4609295e8bf72547d70836871)
|
| |
|
| |
|
| |
|
|
|
|
| |
Also free memory associated with macro name when it is unused.
|
|
|
|
|
|
|
|
| |
Macro constants may now refer to constants defined in source files.
Test case provided by Philip Chimento.
Fixes issues #173 and #75.
|
| |
|
|
|
|
| |
This reverts commit 96c2e06aa661d37ad1cdf31825bbb921125357ae.
|
|\
| |
| |
| |
| | |
Fix parsing when type_specifier comes before type_qualifier.
See merge request GNOME/gobject-introspection!6
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If type_specifier comes after type_qualifier, then GISourceType
representing type_specifier will be merely updated with qualifier
flags. On the other hand, when this order is reversed the type qualifier
used to be attached as a separate node through base_type (with
CTYPE_INVALID), and interpreted incorrectly in transformer code.
This commit changes this behaviour so that information about type
qualifiers is stored directly in GISourceType corresponding to type
specifier. It also fixes analogous issue with storage_class_specifier
and function_specifier.
From higher level viewpoint, it for example represents `const char*` and
`char const*` in equivalent manner after parsing, and addresses issue #79.
|
|\
| |
| |
| |
| |
| |
| | |
Resolve "[PATCH] adding subdir-objects to AM_INIT_AUTOMAKE"
Closes #120
See merge request GNOME/gobject-introspection!2
|
| |
| |
| |
| | |
See #120.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since activating the subdir-objects option, the .c and .h files generated
by Yacc and Lex will show up in the same directory as the source .y and
.l files. The Makefile's BUILT_SOURCES directive should reflect that.
See #120.
|
| |
| |
| |
| |
| |
| | |
autoreconf
See #120.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Preserve complete_ctype when using type from annotation.
Closes #190
See merge request GNOME/gobject-introspection!5
|
|/
|
|
|
|
|
|
| |
When replacing type with one from user annotation we already preserve
ctype, do the same for complete_ctype to preserve const / volatile
qualifiers if any.
Fixes issue #190.
|
|\
| |
| |
| |
| |
| |
| | |
Resolve "giscanner: don't print "suppressed N warnings" if --quiet was specified"
Closes #188
See merge request GNOME/gobject-introspection!1
|
|/ |
|
|
|
|
|
| |
Rico has been doing releases for a long while, and I've picked up the
bug triaging and patch reviews.
|
|
|
|
| |
Re-sync with GLib as of commit a4fc4c1e6eb57b10e2b60f522d11fd2c256dee31.
|
|
|
|
|
|
| |
Releases do not have a Git log, and we lack a way to give people
packaging gobject-introspection an overview of what changed during
the past development cycle.
|
|
|
|
|
|
|
| |
The rules for searching typelib files should be properly documented,
as well as the way to modify the search paths.
https://bugzilla.gnome.org/show_bug.cgi?id=699328
|
|
|
|
| |
You typically want to use the version in GObject, not this one.
|
|
|
|
| |
Integers do not need a transfer annotation.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=761985
|
|
|
|
|
|
|
|
| |
Added the GI_HOST_OS environment variable to eventually specify the host
OS explicitely. It fall backs to os.name to retain backward
compatibility.
https://bugzilla.gnome.org/show_bug.cgi?id=761985
|
|
|
|
|
|
|
| |
The leading `lib` should be passed as part of the shared library name in
the `--shared-library` argument for g-ir-compiler.
https://bugzilla.gnome.org/show_bug.cgi?id=699354
|
|
|
|
|
|
|
| |
Value assignments can happen at any point in the enumeration
declaration.
https://bugzilla.gnome.org/show_bug.cgi?id=629667
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When executing the scanner binary use the PATH/LIB env vars
also under MinGW, since LD_LIBRARY_PATH/rpath doesn't work there.
When resolving the library name from the import library look into
the user provided library paths first before falling back to the
default gcc search path.
This fixes the gir/typelib generation for meson under MSYS2.
Note that MSYS2 ships various patches, so this might not fix it
for all MinGW users.
https://bugzilla.gnome.org/show_bug.cgi?id=791902
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=792714
|
|
|
|
|
|
|
|
| |
ldd commands on *BSD always print the name of the input file regardless
of the number of arguments, so we have to ignore this line to avoid
matching it with _ldd_library_pattern.
https://bugzilla.gnome.org/show_bug.cgi?id=791991
|
|
|
|
|
|
|
|
|
| |
_Thread_local is a C11 keyword, and thread_local is a macro to make it
more confortable to read. As this keyword can only be used in variable
declarations, not in function return values or parameters, it cannot
be included in bindable APIs and we can safely ignore it.
https://bugzilla.gnome.org/show_bug.cgi?id=756921
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The ISO/IEC TS 18661-3:2015 standard added new floating point types to
the C standard.
Newer versions of the GNU C library started exposing `_Float128` in the
headers, which means we need to add this type to the known tokens, to
avoid warnings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is no real limit on the length of an identifier, and some
toolchains easily hit the current limit of 200 characters.
According to this answer on StackOverflow, 2048 seems to be the limit on
MSVC and ICC:
https://stackoverflow.com/questions/6007568/what-is-max-length-for-an-c-c-identifier-on-common-build-systems
So let's use that.
https://bugzilla.gnome.org/show_bug.cgi?id=764791
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This function works fine via introspection
https://bugzilla.gnome.org/show_bug.cgi?id=786665
|