summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.53.51.53.5Rico Tzschichholz2017-08-081-2/+2
|
* gir: Update annotations from GLib 2.53.5Rico Tzschichholz2017-08-082-12/+29
|
* gir: Update glib annotationsFlorian Müllner2017-07-261-5/+8
| | | | | | One of the annotation changes that was pulled in for 1.53.4 broke the introspection ABI and was therefore reverted in master. Pick up the revert now so downstreams can more easily pull in the fix.
* Release 1.53.41.53.4Rico Tzschichholz2017-07-211-2/+2
|
* regress: Test for property and method with conflicting namesRico Tzschichholz2017-07-2114-2/+241
| | | | | | | | | | This is something that libraries are not supposed to do, but some do anyway (Soup and Clutter are two examples) and language bindings should handle it somehow or other. In GJS we want to make sure that the way it's handled doesn't change inadvertently, because buggy library code should not break existing user code. https://bugzilla.gnome.org/show_bug.cgi?id=785091
* gir: Update annotations from GLib git masterRico Tzschichholz2017-07-172-8/+26
|
* MSVC 201x builds: Allow different Python versions per toolsetChun-wei Fan2017-07-121-1/+5
| | | | | | | | | | Use conditionals to select the Python installation, so that we can more stick to the default Visual Studio versions used to compile each official Python releases more closely. This means by default: -2010/2012/2013 builds use Python 3.4.x, which is built with 2010 -2015/2017 builds use Python 3.6.x, which is built with 2015
* Release 1.53.31.53.3Rico Tzschichholz2017-06-201-2/+2
|
* gir: Update annotations from GLib 2.53.3Rico Tzschichholz2017-06-202-29/+555
|
* When handling errors according to errno, catch both IOError and OSErrorSimon McVittie2017-06-192-16/+10
| | | | | | | | | | | | | | | | | | | | | | | | Different Python versions are not completely consistent about the error that is raised and its class hierarchy: Python 3.5.3rc1 (default, Jan 3 2017, 04:40:57) >>> try: open('/foo') ... except Exception as e: print(e.__class__.__mro__) (<class 'FileNotFoundError'>, <class 'OSError'>, <class 'Exception'>, <class 'BaseException'>, <class 'object'>) Python 2.7.13 (default, Dec 18 2016, 20:19:42) >>> try: open('/foo') ... except Exception as e: print e.__class__.__mro (<type 'exceptions.IOError'>, <type 'exceptions.EnvironmentError'>, <type 'exceptions.StandardError'>, <type 'exceptions.Exception'>, <type 'exceptions.BaseException'>, <type 'object'>) This can lead to a race condition during cache cleaning, where two processes both try to delete the same file, and the one that loses the race fails. Signed-off-by: Simon McVittie <smcv@collabora.com> Reviewed-by: Iain Lane <laney@ubuntu.com> Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugzilla.gnome.org/show_bug.cgi?id=772173
* giscanner/utils.py: Fix on non-UNIX-like platformsChun-wei Fan2017-06-151-1/+1
| | | | | | | | | | Commit 85b1d70b93211415d975deff6050f1401743e72d changed the null device from the platform-independent os.devnull to the UNIX /dev/null, which broke introspection builds on non-UNIX-like platforms, as /dev/null is a notion that does not exist on those platforms. Fix this by changing back to os.devnull, but still opening it as writable. https://bugzilla.gnome.org/show_bug.cgi?id=781312
* Visual Studio builds: Use the Centricular fork of libffiChun-wei Fan2017-06-148-44/+35
| | | | | | | | | The upstream libffi is getting bit-rotten on the regards of Windows/MSVC builds, and we are eventually moving towards to the Meson build system, so make use of the Centricular fork of libffi[1] which is better maintained and tested for Windows/MSVC builds. [1]: https://github.com/centricular/libffi
* Release 1.53.21.53.2Rico Tzschichholz2017-05-231-2/+2
|
* gir: Update annotations from GLib 2.53.2Rico Tzschichholz2017-05-231-2/+2
|
* g-ir-inspect: Ensure variables are at the top of blockChun-wei Fan2017-05-181-1/+2
| | | | | We did not yet advertise C99 requirements for G-I yet, so let's not assume this yet.
* Add a test for "(in) (transfer floating)" parameters beeing an alias for ↵Christoph Reiter2017-05-176-5/+37
| | | | | | | | | | | | | | | | | | | | | "(in) (transfer none)". The "(in)" alias was (unintenionally?) introduced in https://git.gnome.org/browse/gobject-introspection/commit/?id=699ad0fec427c79bec1 which added an alias for return annotations. This change makes sure that this continues to work. Functions which ref_sink in params are currently marked as transfer-none since in the case of non-floating objects (which all bindings use) no ownership gets transfered. But in case of floating objects, which is the common case when using the C API directly, the ownership _is_ transfered. Using transfer-floating should make this clearer while giving the same result for bindings. Functions where this could be used: gst_bin_add, gtk_container_add, gst_element_add_pad See https://bugzilla.gnome.org/show_bug.cgi?id=657202 and https://bugzilla.gnome.org/show_bug.cgi?id=702960 https://bugzilla.gnome.org/show_bug.cgi?id=742618
* scanner: Fix non-libtool linker flags on DarwinPhilip Chimento2017-05-171-1/+1
| | | | | | | | | Darwin's linker doesn't like "-rpath=path"; instead pass "-rpath path", which works on more linkers than the version with the = sign does. Regressed in commit 5d4cd25292b8ed2c7a821ebe19fc5ab5d447db1a. https://bugzilla.gnome.org/show_bug.cgi?id=781525
* gir: Update annotations from GLib git masterRico Tzschichholz2017-05-132-40/+217
|
* Include missing types from cairoNicola Fontana2017-05-091-0/+581
| | | | | | | Update cairo-1.0.gir.in to include all the exported types, e.g. cairo_device_t and a bunch of enumerations. https://bugzilla.gnome.org/show_bug.cgi?id=743364
* cairo_font_type_t is a GEnumNicola Fontana2017-05-091-1/+19
| | | | | | Properly register cairo_font_type_t with its enumerated values. https://bugzilla.gnome.org/show_bug.cgi?id=743364
* Use proper GLib values for cairo_content_tNicola Fontana2017-05-091-3/+3
| | | | | | | The enum values, as generated by glib-mkenums, are by convention in lowercase and separated with underscores. https://bugzilla.gnome.org/show_bug.cgi?id=743364
* Correct wrong GLib type name for cairo_content_tNicola Fontana2017-05-091-1/+1
| | | | | | | | Enumerations in cairo-gobject do not follow the GLib naming conventions (i.e., CamelCase); they have been registered using their original C names instead, e.g. "cairo_content_t" instead of "CairoContent". https://bugzilla.gnome.org/show_bug.cgi?id=743364
* CairoFontOptions is a GBoxed typeNicola Fontana2017-05-091-1/+3
| | | | | | | cairo-gobject has wrapped cairo_font_options_t in a GBoxed since the beginning. Make it explicit also in the repository file. https://bugzilla.gnome.org/show_bug.cgi?id=743364
* Use tab consistently in cairo.gir.inNicola Fontana2017-05-091-14/+14
| | | | | | | All the source but a fistful of lines uses tab for 8-spaces indenting and left-align attribute names: let's fully embrace this convention. https://bugzilla.gnome.org/show_bug.cgi?id=743364
* g-ir-{compiler,generate,inspect}: Call setlocale in main functionTing-Wei Lan2017-05-053-0/+10
| | | | | | It is required to correctly show translated messages on some locales. https://bugzilla.gnome.org/show_bug.cgi?id=760419
* Revert "removing $(srcdir) because it is not replaced correctly and not ↵Emmanuele Bassi2017-05-046-21/+21
| | | | | | | | necessary" This reverts commit 17ef691e9b3ebd475b01d1e623d3df7b1f534dfa. This breaks builddir != srcdir builds, like GNOME Continuous.
* Revert "build: Use $(srcdir) when calling Python scripts"Emmanuele Bassi2017-05-043-3/+3
| | | | This reverts commit b1200a87bc0bd4f4fcd5275f25422032104138ed.
* build: Use $(srcdir) when calling Python scriptsEmmanuele Bassi2017-05-043-3/+3
| | | | | | We need to point Python in the right direction, because unlike source rules, automake won't automatically expand commands in explicit make rules.
* build: Install the gir-1.2 schema system-widePhilip Withnall2017-05-041-0/+4
| | | | | | | | Install the schema to $(datadir)/glib-2.0/schemas, so that projects which depend on GLib can validate their GIR files at build or distribution time. https://bugzilla.gnome.org/show_bug.cgi?id=774019
* removing $(srcdir) because it is not replaced correctly and not necessaryKarl-Philipp Richter2017-05-046-21/+21
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=744021
* giscanner: Do not use distutils for linkingChun-wei Fan2017-05-032-115/+86
| | | | | | | | | | | | | | | | | | | | | | | | ...the dumper program for all cases. It turned out that using distutils for linking is more troublesome than useful as we need to ensure that the paths specified by -L need to come before the standard library search paths, and distutil's ccompiler.add_library_path() and ccompiler.add_runtime_library_path() does not work for all of its supported compilers (Visual Studio is an example). Instead, we go back to constructing our linker command line manually as we did before (and as we now do in the libtool case), but with some enhancements: -Use '-libpath:' on Visual Studio builds, which corresponds to the -L flag on GCC/CLang. -Extend LIB/PATH (Windows/Visual Studio) or LD_LIBRARY_PATH (other compilers/envs), which is necessary as we resolve the libraries that are passed into g-ir-scanner, at least on Windows. -Don't attempt to link to or resolve m.lib on Visual Studio builds, as the math functions are in the standard CRT .lib/.dll, and there is no such thing as m.lib https://bugzilla.gnome.org/show_bug.cgi?id=781525
* giscanner: Update location of temp sources and objectsChun-wei Fan2017-05-012-3/+4
| | | | | | | | | | | | | | For preprocessing, when we create the temp file for preprocessing, make the temp file be stored in CWD instead of the system's temp directory; and when we compile the dumper program, set the output_dir to be the root directory (<drive letter>:\ on Windows and / otherwise). This is because distutils insists on using the full path from the root directory to compile sources, so that if we set the output_dir as we now do we will get $(abs_srcdir)/$(tmpdir)/<$(abs_srcdir)_minus_rootdir>/$(tmpdir)/<target_gir_file_name>.[o|obj]. https://bugzilla.gnome.org/show_bug.cgi?id=781525
* scannerparser.y: Really remove temp .h file on WindowsChun-wei Fan2017-05-011-1/+2
| | | | | | | | | | | | | In gi_source_scanner_parse_macros(), a temporary .h file is generated during the process of parsing the macros, and they aren't being deleted on Windows. In turns out that the g_unlink() call in that function failed because Windows does not allow one to unlink/delete files while they are open, and that the g_unlink() call is done way early (for some reason). Fix this by calling fclose() on the fmacros FILE* *after* we are done with fmacros, and then finally call g_unlink() on the temp .h file. https://bugzilla.gnome.org/show_bug.cgi?id=781525
* Release 1.53.11.53.1Rico Tzschichholz2017-04-251-2/+2
|
* gir: Update annotations from GLib 2.53.1Rico Tzschichholz2017-04-252-16/+16
|
* regress: Add test for setting a NULL strv in a GValueSam Spilsbury2017-04-257-0/+121
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=775679
* Visual Studio 201x builds: Fix "installation"Chun-wei Fan2017-04-181-1/+1
| | | | The .lib file was not copied from the right place, fix that.
* Fix 'Bad file descriptor' error when checking libtool versionSam Thursfield2017-04-151-1/+1
| | | | | | | | | | | | Running g-ir-scanner on Fedora 25 (libtool 2.4.6) produces the following message on stderr, twice: /usr/bin/libtool: line 2460: printf: write error: Bad file descriptor This is because we were redirecting stdout to /dev/null incorrectly -- we were opening /dev/null for reading rather than for writing. https://bugzilla.gnome.org/show_bug.cgi?id=781312
* gir: Update annotations from GLib git masterRico Tzschichholz2017-04-104-34/+148
|
* Bump version to 1.53.0Rico Tzschichholz2017-04-101-3/+3
|
* Release 1.52.11.52.1Rico Tzschichholz2017-04-101-2/+2
|
* gir: Update annotations from GLib 2.52.1Rico Tzschichholz2017-04-103-13/+52
|
* tests: Add marshalling tests for GValue-valued propertiesPhilip Chimento2017-04-032-0/+22
| | | | | | This is to test GJS's support of GValues boxed inside GValues. https://bugzilla.gnome.org/show_bug.cgi?id=688128
* gimarshallingtests: Add a flags and enum propertyChristoph Reiter2017-03-282-0/+32
| | | | | | | These will be used by pygobject in https://bugzilla.gnome.org/show_bug.cgi?id=726484 https://bugzilla.gnome.org/show_bug.cgi?id=780652
* g-ir-scanner: fix wrong order of -L options in libtool invocationSebastian Geiger2017-03-261-2/+4
| | | | | | | This patch fixes an issue in dumper.py, which causes a wrong oder of -L options to be passed to libtool. This in turn can cause build failures if old library files are present in the linked library directories. https://bugzilla.gnome.org/show_bug.cgi?id=778507
* giscanner: Use shlex.split() for environment variablesNirbheek Chauhan2017-03-212-7/+6
| | | | | | | | | | | | | | str.split() does not handle quoting, so if you have spaces in your CFLAGS, it will be split incorrectly. For instance: CFLAGS="'-I/opt/some dir' -DFOO=bar" >>> os.environ['CFLAGS'].split() ["'-I/opt/some", "dir'", '-DFOO=bar'] >>> shlex.split(os.environ['CFLAGS']) ['-I/opt/some dir', '-DFOO=bar'] https://bugzilla.gnome.org/show_bug.cgi?id=778971
* Release 1.52.01.52.0Rico Tzschichholz2017-03-201-3/+3
|
* gir: Update annotations from GLib 2.52.0Rico Tzschichholz2017-03-201-2/+3
|
* tests: Update "expected" for Regress-1.0.girRico Tzschichholz2017-03-201-1/+1
|
* typedefs: fix type information.Mathieu Duponchelle2017-03-143-9/+2
| | | | | | | | | | | We now reuse _create_type_from_base instead of reimplementing it in a semi-broken way in transformer, and use complete_ctype when writing it out if available. This incidentally allows us to remove a test where the comment acknowledged the non-optimal behaviour. https://bugzilla.gnome.org/show_bug.cgi?id=779959
View Lorry Controller Status