summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* release1.59.3Christoph Reiter2019-01-081-0/+19
|
* Update glib annotationsChristoph Reiter2019-01-081-2/+16
|
* tests: add some tests for get_source_root_dirsChristoph Reiter2019-01-084-3/+35
| | | | | To make it easier to test make sure it always returns absolute paths. Also fix a typo, oops!
* get_source_root_dirs: handle empty file list case. Fixes #257Christoph Reiter2019-01-081-0/+3
| | | | | | While scannermain checks that at least one filename is given, it filters them based on the file extension after that, so we still need to handle an empty file list laster on.
* meson: use underscore as a separator in build optionsChristoph Reiter2019-01-076-11/+11
| | | | This is what https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting suggests.
* scanner: Flatten multi-dimensional arrays fieldsTomasz Miąsko2019-01-074-10/+85
| | | | | | | | | | | | | Provide partial support for multi-dimensional arrays by representing them as flattened one dimensional array with size that is equal to product of sizes in each dimension. Previously only the first dimension would be actually used. This should be sufficient to ensure that those fields have layout compatible with C, without using nested array types that are currently unsupported by vapigen Issue #255.
* scanner: Remove incorrect c:type generated for array of synthesized unionsTomasz Miąsko2019-01-062-5/+3
| | | | | | | | This also reverts workaround introduced to support this use case in f77cfc4275b1fba4f9fedea6e40b00e0ebbe142c, since it is no longer necessary. Fixes issue #141.
* scanner: Remove incorrect c:type from fields with array typeTomasz Miąsko2019-01-063-26/+11
| | | | | | | | | | Neither `_create_source_type` nor `_create_complete_source_type` actually support fixed size arrays, so previously generated C types were incorrect. Remove C types from array fields instead of producing incorrect ones. Fixes issue #145.
* ci: use the pkg-config.exe hosted by meson since sourceforge is flakyChristoph Reiter2019-01-061-3/+2
|
* scanner: rework source root guessing codeChristoph Reiter2019-01-061-3/+24
| | | | | | | | | | | | commonprefix doesn't work on relative paths and doesn't return directories so so for the g-i build case it returned an empty string resulting in paths relative to the working directory, making the build not reproducible. To somehwat improve this make sure the paths are absolute, use commonpath and if no common dir can be found just fall back to passing all directories so we only write the basenames. I guess we should look into passing --sources-top-dirs in the g-i build.
* meson: set libdir/bindir relative to exec_prefixChristoph Reiter2019-01-061-2/+2
| | | | To match what autotools produces
* meson: remove an unused helper scriptChristoph Reiter2019-01-061-16/+0
|
* meson: warn that not all tests will be run if building without cairo/doctoolChristoph Reiter2019-01-064-4/+11
|
* scanner: Merge specifiers and qualifiers when merging basic types.Tomasz Miąsko2019-01-052-1/+6
|
* scanner: Merge basic types in `specifier_qualifier_list` production.Tomasz Miąsko2019-01-059-195/+257
| | | | | | | | | | | This is necessary to parse types like `unsigned char` or `long double`, and is already done when parsing `declarations_specifiers`. Examples that are fixed by this change include: * `GLib.TestLogMsg.nums` previously parsed as `long` but should be `long double`. * `GMime.Encoding.uubuf` previously parsed as `unsigned` but should be `unsigned char`.
* website: add cppgir C++ bindingMark Nauwelaerts2019-01-051-0/+1
|
* version bumpChristoph Reiter2019-01-042-2/+2
|
* release1.59.2Christoph Reiter2019-01-041-0/+27
|
* autotools: dist test_docwriter.pyChristoph Reiter2019-01-041-1/+2
|
* meson: disable doctool by defaultChristoph Reiter2019-01-033-3/+3
| | | | To unbreak continuous
* meson: port doctool testsChristoph Reiter2019-01-033-0/+73
|
* tests: try building Bar-1.0 againChristoph Reiter2019-01-021-1/+36
| | | | This time pass the libgirepository build dir
* ci: update meson to 0.49.0Christoph Reiter2019-01-025-5/+5
|
* gimarshallingtests: Remove declarations of nonexistent functionsPhilip Chimento2019-01-011-8/+0
| | | | | | | These functions were removed a long time ago in commit af7be95a. Being present in the header file means they are present in the generated GIR file, but trying to resolve them with dlsym will fail and crash the program.
* meson: port more typelib testsChristoph Reiter2019-01-014-31/+141
|
* ci: enable -Werror for msys2+mesonChristoph Reiter2019-01-014-6/+13
|
* meson: make test_offsets.py work on WindowsChristoph Reiter2019-01-011-6/+7
| | | | | meson doesn't set PATH for the test dependencies so we have to do it manually. Also make sure the test depends on the test binary.
* gitestoffsets: use g_fprintf and fix the format specifier for the struct offsetChristoph Reiter2019-01-011-19/+20
| | | | | | | G_GSIZE_FORMAT should only be used with glib functions and G_STRUCT_OFFSET() returns glong not gsize. This fixes various compiler warnings on Windows.
* autotools: fix missing version api in gtk-doc for non-srcdir buildsChristoph Reiter2019-01-011-2/+2
| | | | | | Properly pass the build dir paths to gtk-doc so it can find things in giversion.h This fixes the version section being empty when building the docs with non-srcdir autotools.
* tests: add the utility dep to the right targetChristoph Reiter2019-01-011-2/+2
| | | | I added it to the wrong one in d2bd6390ed8, oops..
* tests: revert building Bar-1.0.girChristoph Reiter2019-01-011-26/+1
| | | | | It broke continuous https://build.gnome.org/continuous/buildmaster/builds/2019/01/01/0/build/log-gobject-introspection.txt
* meson: port more gir testsChristoph Reiter2019-01-011-0/+92
|
* meson: fix missing regress dependency on the utility gir.Christoph Reiter2018-12-311-2/+3
|
* meson: build libregress with cairo supportChristoph Reiter2018-12-313-8/+40
| | | | | The cairo dependency fallback code is copied from pygobject. I assume that will work for msvc users (cairo is disabled by default anyway)
* meson: port some .gir testsChristoph Reiter2018-12-311-0/+271
|
* Update glib annotationsChristoph Reiter2018-12-313-44/+356
|
* customize_compiler: also replace the linker command if CC is setChristoph Reiter2018-12-302-1/+9
| | | | | | | | 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
* Update NEWSChristoph Reiter2018-12-301-0/+12
|
* Do not bail out when parsing GIR files without doc positionsEmmanuele Bassi2018-12-291-2/+2
| | | | | | | The position attributes on a <doc> element are not mandatory, so we should have some fallback value if they are missing. Fixes: #252
* tests: Use macros to print field offsetsTomasz Miąsko2018-12-291-60/+63
|
* tests: Drop separate functions for offsets testsTomasz Miąsko2018-12-291-56/+11
|
* tests: Use macro to determine alignmentTomasz Miąsko2018-12-291-49/+9
|
* ccompiler: don't use Python compiler flags. Fixes #150Christoph Reiter2018-12-292-8/+8
| | | | | | | 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.
* ccompiler: include a version of customize_compiler() from CPythonChristoph Reiter2018-12-291-1/+50
| | | | | | | | 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!
* Test commands executed by unix C compiler.Tomasz Miąsko2018-12-294-1/+222
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* tests: Remove temporary files created when testing transformerTomasz Miąsko2018-12-221-4/+7
|
* scanner: make using bool without stdbool include work again. Fixes #247Christoph Reiter2018-12-213-1/+7
| | | | | | | | | 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.
* docwriter: Support markdown 3.x. Fixes #250Christoph Reiter2018-12-202-5/+16
| | | | | 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.
* tests: make scanner tests work with msvc + subprojectsChristoph Reiter2018-12-204-28/+44
| | | | | | | | 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.
* Cleanup strict-prototypes warningsTomasz Miąsko2018-12-203-5/+4
|
View Lorry Controller Status