| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
We want to use bzip2 since that's what Fedora uses.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We're handling GVariant at least internally now. Potentially
we could support earlier, but eh.
|
| |
|
| |
|
|
|
|
|
| |
This enables glib documentation to be added to the generated gir using the original source
eg. --with-glib-src=/usr/src/glib
|
|
|
|
|
| |
Add an infrastructure for testing warnings, add two
examples how to verify warnings
|
|
|
|
|
| |
No official release yet, but this allows consumer configure.ac
to check for a new enough version.
|
|
|
|
|
|
| |
We get better testing through the bindings, having hand-written
.gir files is a maintenance pain, and it uses the --code option
to g-ir-compiler which we also don't want to support.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we had both e.g. GI_TYPE_TAG_LONG and GI_TYPE_TAG_INT64,
but in fact the typelib is already machine-specific, so it makes sense
to just encode this as a fixed type. The .gir remains abstract.
We also remove size_t from the typelib; one would never want to treat
it differently than an integer.
time_t is removed as well; while bindings like gjs had special handling
to turn it into e.g. a JS Date object, I don't think we should encourage
people to use these POSIX types in their API. Use GTimeVal or the like
instead.
Because the typelib is now really machine-specific, we need to remove
the -expected.tgirs from git. (We could potentially add a check
which wasn't just a literal diff later)
https://bugzilla.gnome.org/show_bug.cgi?id=623774
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Don't try to build the everything library nor the gir if we
can't find cairo. Pass in the right flags so it can be built
when cairo is not in the same prefix as the rest of the dependencies.
|
|
|
|
| |
This allows us to not hard depend on cairo.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is required as external projects such as gjs
are now using girffi and thus need the ffi cflags
to be able to link.
https://bugzilla.gnome.org/show_bug.cgi?id=603653
|
|
|
|
|
| |
This reverts commit 92abbe78dd7ffe0ff6d61db5f2bff0745a69115a and
494c1c92520917999407832453c11c2247b4e7bb.
|
| |
|
|
|
|
|
|
|
| |
We use it for girffi.h. Remove the code to detect libffi without the .pc
file. If you don't have it, get it.
https://bugzilla.gnome.org/show_bug.cgi?id=603653
|
| |
|
| |
|
|
|
|
| |
Shave is just way too invasive in the build system.
|
|
|
|
| |
Others like byacc barf on some of the directives like %error-verbose.
|
|
|
|
|
|
| |
Some projects may want to avoid the giant -Wl,--export-dynamic
hammmer and instead use a custom regexp or export list, so
provide a .pc file for them to use.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When ./configure --prefix $HOME/some/where is used gobject-introspection
will happily install the files into $HOME/some/where/data/gir-1.0 but
it will refuse to find them. Apply the same trick as in
girepository/girepository.c:init_globals to find the gir files.
Unifiy the name gir-1.0 in GIR_SUFFIX and use it throughout the
project, introduce GIR_DIR which holds the path to the gir files and
update girparser and transformer.py to look into this path.
|
|
|
|
|
| |
Everything isn't a test for quite a while now, it's a public library.
So move it to gir/.
|
|
|
|
| |
This avoids issues with unexpanded variables, i.e. ${exec_prefix}/libdir
|
|
|
|
|
|
| |
We don't want to pollute the global namespace with our private
libraries. Also, this sidesteps all the craziness that is happening
with OS vendors changing how Python installs modules.
|
|
|
|
|
|
| |
patching hard
We'll just require 1.12, which is the version fixed to work with shave.
|
|
|
|
| |
Which let's us focus on the important warnings.
|
|
|
|
|
|
|
|
|
|
| |
to SUBDIRS
The gtk-doc introductory commit introduced some generated files; remove those.
We apparently only require 1.11, so downgrade to that.
Finally, the docs directory was missing from the toplevel SUBDIRS.
|
| |
|
| |
|