summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix misleading documentation for `closure` annotationwip/tintou/closure-documentationCorentin Noël2019-06-231-4/+4
|
* girepository: Return pointer array for interface cachePhilip Chimento2019-06-203-4/+28
| | | | | | | | | | | | | In g_irepository_get_object_gtype_interfaces(), returning the address of the first GIBaseInfo* does not work reliably, because the GIBaseInfos are not necessarily stored contiguously. So the second and subsequent ones might be garbage. Instead, return the address of the array of GIBaseInfo pointers. Add a test that verifies the functionality, as well. This is unfortunately an API and ABI break.
* Update NEWSChristoph Reiter2019-06-151-0/+13
|
* Update glib annotationsChristoph Reiter2019-06-153-565/+539
|
* meson: set a default cairo dll name for the MSVC buildChristoph Reiter2019-06-131-1/+5
| | | | | | | | The cairo MSVC build produces a cairo-gobject.dll unlike the libcairo-gobject-2.dll with autotools. While one can pass the right DLL name through the cairo_libname option, having a better default can't hurt.
* Add Vulkan girMatthew Waters2019-06-033-0/+852
|
* gi-test: Fix gir file testsChun-wei Fan2019-05-021-1/+1
| | | | | | | | | | | | | | | | | | | Meson unfortunately does not normalize the paths for us, so we couldn't just rely on it to give us the correct target name without the full target path when the path separator is not '/' (such as on Visual Studio builds, where the path separator is '\\' (with escape character). This means that, that on Visual Studio builds, targetname would be: D:\\gi.build\\tests\\scanner\\Typedefs-1.0.gir instead of: Typedefs-1.0.gir Since we have the targetbase variable which actually has the correct info we need, use that to deduce the correct reference .gir file to compare to.
* build: Force-include msvc_recommended_pragmas.h on Visual StudioChun-wei Fan2019-04-307-58/+94
| | | | | | | | | | By doing so, we essentially cover the various compiler flags that we want to use for non-Visual Studio builds to check for warnings that might cause real concern. This also skips the checks for the various GCC-isque CFlag checks that are scattered in the various build files on Visual Studio builds, since they are essentially meaningless on Visual Studio builds.
* giscanner/scannerlexer.l: Include io.h on WindowsChun-wei Fan2019-04-301-0/+2
| | | | | | | | This is to compensate the for the lack of unistd.h on Visual Studio builds, and to avoid the compiler warning about the implicit declaration of access() as a result. This is to also prepare for the next commit when we force-include msvc_recommended_pragmas.h from GLib on Visual Studio builds.
* scanner: Fix error on Windows in case source files are on different drivesChristoph Reiter2019-04-212-1/+16
| | | | | | | | | os.path.commonpath() raises ValueError if the paths given to it are on different drives. Handle that case by giving up and add a test. Reported here: https://github.com/msys2/MINGW-packages/pull/5258#issuecomment-485230864
* meson: fix default cairo DLL name on WindowsChristoph Reiter2019-04-201-1/+1
| | | | host_machine.system() returns "windows" on Windows
* cachestore: handle cache getting deleted while loading it. Fixes #278Christoph Reiter2019-04-171-3/+7
| | | | | | | | In the unlucky event where the cache gets deleted after the os.path.exists() check but before we get its mtime things would error out. Instead of using os.path.exists() handle the exceptions of the operations which we expect to possibly fail.
* regress: Check array length before accessingPhilip Chimento2019-04-152-37/+43
|
* regress: Initialize all struct fields, or mark intent not toPhilip Chimento2019-04-151-4/+4
| | | | | | | In some cases we don't initialize all the struct fields of Regress structs. We should either initialize them all, in the case of fields that were added later; or mark that we don't intend to initialize them all, by using C99 designated initializers.
* tests: Mark unused function arguments with G_GNUC_UNUSEDPhilip Chimento2019-04-154-222/+247
| | | | | | | These files are exported for other projects to compile, so they should compile with as few compiler warnings as possible. If GJS or PyGObject has -Wunused-parameter turned on, then there should not be warnings in these files.
* giscanner: Allow fields which are callbacksPhilip Chimento2019-04-071-1/+1
| | | | This is apparently used in Gee-0.8 and Folks-0.6.
* docwriter: Fix Exception message attributePhilip Chimento2019-04-071-1/+1
| | | | | This may have been a leftover from Python 2. Exception('message') does not automatically set a message attribute on the exception object.
* Update NEWSChristoph Reiter2019-04-071-0/+10
|
* meson: always pass --qiet to g-ir-scannerChristoph Reiter2019-04-074-0/+16
| | | | Less noisy build
* updated thanks to comments from reviewersDavid Bellot2019-04-021-10/+11
|
* docs: finally transformed tabs to spaces in GIR xml relaxng fileDavid Bellot2019-04-021-164/+164
|
* docs: added missing docs for annotations attributeDavid Bellot2019-04-021-0/+3
|
* docs: added complete documentation as comments in the RelaxNG schemaDavid Bellot2019-04-021-21/+217
|
* shlibs: fall back to basename on macOS for relative paths. Fixes #222Christoph Reiter2019-03-252-12/+44
| | | | | | | | | | | | | | | | | | | On macOS we ideally want to write the final absolute path of the library into the gir and typelib. Up until now we inferred the install path from the .la file in case we used libtool and through otool in case we weren't using libtool hoping that the install_name was matching the install path. meson currently sets the install_name of libraries to "@rpath/foo.dylib" and adds rpaths to the executables in the build dir. Only during install does it change the install_name to the absolute target path in all places. Since we get called during build time we only get the @rpath from otool, which then makes things fail at runtime since the executables don't have the matching rpath set. To make this somewhat work just fall back to the basename for relative paths, so we dlopen "foo.dylib" and depend on things being in /usr/local/lib or DYLD_FALLBACK_LIBRARY_PATH including the lib path (see man dlopen)
* docs: include '--c-include' in g-ir-scanner man page. Fixes #275Christoph Reiter2019-03-242-0/+8
|
* tests: Fix compatibility with Python 3.5Tomasz Miąsko2019-03-151-2/+2
| | | | | | | | Use call_count to verify the number of calls. This replaces assert_called_once used previously, which is only available since Python 3.6. Fixes issue #274.
* ci: test with Python 3.5Christoph Reiter2019-03-153-7/+36
|
* Drop autotools build systemChristoph Reiter2019-03-1122-2051/+0
|
* MSVC.README.rst: Update VS 2008/x64 build notesChun-wei Fan2019-03-111-3/+4
| | | | | | | It appears that tests/repository/gitypelibtest.c needs to be added to the list of files that we must change the optimization flag from /O2 to /O1 in order that the Visual Studio 2008 x64 compiler does not hang, due to compiler optimization issues.
* Update NEWS; version bumpChristoph Reiter2019-03-103-3/+13
|
* Update glib annotationsAndrea Azzarone2019-03-072-1/+11
|
* version bumpChristoph Reiter2019-03-042-2/+2
|
* release1.59.5Christoph Reiter2019-03-041-0/+8
|
* Update glib annotationsChristoph Reiter2019-03-043-76/+32
|
* gir: skip glib-enumtypes.h for GObject-2.0. See #267Christoph Reiter2019-03-042-2/+2
| | | | | | | | | The newly added GTypes in glib!481 result in g-i generating an enum type in GLib-2.0 and a GType based one in GObject-2.0. This makes problems for the dlang bindings (see #267) so skip them for now. Ideally we should include it in GLib-2.0 like we do with glib-types.h.
* ccompiler: restore customize_compiler() setup for macOS. See #268Christoph Reiter2019-03-021-0/+7
| | | | | | | | | The original customize_compiler() calls into _osx_support.customize_compiler() the first time it is used and I didn't copy it in !118 because it is private API. Issue #268 points out that the macOS build is broken now so I guess that was important in some way. Make sure the setup code is run by calling the original customize_compiler() with a dummy compiler instance.
* website: Add link to C/typelib ABI cross-validatorTomasz Miąsko2019-02-131-0/+1
|
* gir: Include C header in cairo gir fileTomasz Miąsko2019-02-131-0/+1
|
* version bumpChristoph Reiter2019-02-042-2/+2
|
* release1.59.4Christoph Reiter2019-02-041-0/+14
|
* Fix a possible use-after-free.Elliott Sales de Andrade2019-02-021-1/+1
| | | | | | If g_mapped_file_new fails, then `version` will be freed, but it was already added to the hash table. This means there could be a use-after-free while doing a lookup on the hash table the next time.
* Fix possible leak of transitive dependency name.Elliott Sales de Andrade2019-02-021-1/+2
| | | | | | If a transitive dependency appears twice, the original pointer will be removed from the hash table. Since these names were created by g_strsplit, they need to be freed, or they will leak.
* Update glib annotationsChristoph Reiter2019-02-012-24/+409
|
* repository: Fix annotation for g_irepository_get_object_gtype_interfaces()Rico Tzschichholz2019-01-161-2/+2
| | | | Introduced by 9826d952358c8330d72ecba062f489fbdc31bbd1
* Revert "Restore original meaning of disguised attribute."Christoph Reiter2019-01-166-8/+28
| | | | | | This reverts commit f606183a010fbec4382acb728882cc0eddbaf7f7. See https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/9#note_409979
* maintransformer: Don't warn on (optional) annotations on (inout)Guido Günther2019-01-132-7/+8
| | | | This makes the scanner consistent with the docs.
* autotools: don't pass all the libregress cflags to the scanner. Fixes #226Christoph Reiter2019-01-121-1/+4
| | | | | | | | | | | | They contain things like -fvisibility=hidden which, in case of building with CFLAGS="-flto -O2" LDFLAGS="-Wl,--as-needed -flto", results in the linker throwing out unused symbols and not linking the dumper against libregress. This results in errors like: Invalid GType function: 'regress_test_enum_get_type' Failed to find symbol 'regress_test_enum_get_type' Fix this by only passing the required CFLAGS to the scanner instead.
* Restore original meaning of disguised attribute.Tomasz Miąsko2019-01-106-28/+8
| | | | | | | | | | | | | | | | > Certain types like GIConv and GdkAtom are pointers internally but don't > look like pointers when referenced. They have the form. > > typedef struct _X *X; > > Parse these as structures/records but mark them in the gir with a 'disguised' > attribute so that we know that they need special handling. Additionally, stop relaying on disguised attribute when deciding whether to render a page. Check number of fields instead, so as to avoid introducing large regression in the docs. Fixes #101.
* message: handle fatal errors even if warnings are disabled. Fixes #229Christoph Reiter2019-01-101-1/+1
|
* maintransformer: when the namespace is empty use error() instead of fatal()Christoph Reiter2019-01-101-1/+1
| | | | | | | | | | | network-manager is calling things like this during configure: g-ir-scanner --namespace=test --library=c /dev/null --output /dev/null to test if the scanner is working. This results in a fatal error, but beause of #229 was ignored. Do keep this working after we fix #229 downgrade this to a simple recoverable error message. An empty namespace doesn't prevent the scanner from creating a .gir file so this should be fine.
View Lorry Controller Status