summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Add constant value annotationJohan Dahlin2011-09-144-8/+54
| | | | | Add an annotation tag "Value:" which can be used on constants to override the value.
* tests: Add gir/ to toplevel typelib pathColin Walters2011-09-131-1/+1
| | | | Fixes the test when running uninstalled.
* Fix g_type_info_is_pointer() for overriden types of arguments.Pavel Holejsovsky2011-09-121-0/+39
| | | | | | | | | Algorithm which detects whether argument type is pointer checks for trailing '*' characters in c:type .gir elements. This failed if ctype is either 'gpointer' or 'gconstpointer'. Add specific check for gpointer/gconstpointer types when deducing pointerness of the type. https://bugzilla.gnome.org/show_bug.cgi?id=658848
* scanner: correctly handle structs with arrays of anon unionsTorsten Schönfeld2011-09-114-1/+83
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This applies mainly to GValue, which is defined as: struct _GValue { /*< private >*/ GType g_type; /* public for GTypeValueTable methods */ union { gint v_int; guint v_uint; glong v_long; gulong v_ulong; gint64 v_int64; guint64 v_uint64; gfloat v_float; gdouble v_double; gpointer v_pointer; } data[2]; }; Previously, the scanner did not understand the array of unions. This resulted in g_struct_info_get_size returning an incorrect size for GValue (at least on 32bit systems). Fix this by making up a separate union declaration for the GIR that can be referenced by the array. https://bugzilla.gnome.org/show_bug.cgi?id=657040
* scanner: Add "notify" signal to GObjectColin Walters2011-09-091-0/+9
| | | | | For gjs we want to switch to using introspection data for signals, and the "notify" signal being missing from GObject was a problem.
* Windows port: disable barapp test program on WindowsDieter Verfaillie2011-09-071-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=620566
* Windows port: set CAIRO_LIBS in LIBADD, not LDFLAGSDieter Verfaillie2011-09-071-1/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=620566
* regress: Fix wrong type of variable in regression testVincent Untz2011-09-021-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=658075
* gimarshallingtests.h: Remove unimplemented functionsGOBJECT_INTROSPECTION_1_29_17Colin Walters2011-08-291-4/+0
| | | | The new missing-element-type warning triggers for these.
* scanner: Don't try to copy c:type if we're parsing (element-type)Colin Walters2011-08-293-52/+52
| | | | | | | | | | | | | Commit 81abc2eb63317003a11d1484e84698a37e8ec035 tries harder to keep the c:type if it was overriden by a (type) annotation. However, the _resolve() function was also called for (element-type), which had undesirable effects - we'd copy the container c:type to the element type. Fix this by splitting out the c:type preservation to only happen when processing toplevel types. https://bugzilla.gnome.org/show_bug.cgi?id=656931
* Fix warning for missing (element-type)Colin Walters2011-08-293-0/+13
| | | | | | While looking for a different bug, I noticed that the introspectable pass lists was missing GSList. And the warning was never set up to fire anyways. Fix it and add a test.
* add regression test for skipped #defineXavier Claessens2011-08-262-0/+8
|
* Add a regress test for a method returning GPtrArrayXavier Claessens2011-08-263-0/+29
|
* add back the fixed_array_out_struct testJohn (J5) Palmieri2011-08-231-0/+22
|
* tests: build tests only on make checkAlexandre Rostovtsev2011-08-233-15/+9
| | | | | | | | | | | | Use automake's check_ prefix and avoid putting anything nontrivial in BUILT_SOURCES so that tests are build only on make check. The dummy -rpath in AM_LDFLAGS in tests/scanner/Makefile.am is needed to force libtool to build shared libraries for check_LTLIBRARIESS targets (automake builds check_LTLIBRARIES as static by default); see http://lists.gnu.org/archive/html/automake/2005-10/msg00107.html https://bugzilla.gnome.org/show_bug.cgi?id=657066
* doctool: Disable tests for nowColin Walters2011-08-231-19/+21
| | | | | They don't work for multiple reasons, and there is still debate about how the formatting etc. will work.
* Add tests for newly added warningsGiovanni Campagna2011-08-181-1/+27
| | | | | g-ir-scanner now warns for invalid (element-type) annotations in GPtrArray and in GByteArray. Test that.
* tests/doctool: Remove MALLARD_DIRS from BUILT_SOURCESTomeu Vizoso2011-08-181-1/+0
| | | | so we don't generate the test docs when doing a plain build
* Disallow non byte types for GByteArraysGiovanni Campagna2011-08-181-1/+1
| | | | | | | | | Similarly to GPtrArrays, GByteArrays can only contain bytes. Emit a warning if an inconsistent (element-type) is placed, and ensure that the default is guint8 if nothing is added. This way bindings can support GByteArrays without special casing them. https://bugzilla.gnome.org/show_bug.cgi?id=652753
* Forbid GPtrArrays holding non-pointer typesGiovanni Campagna2011-08-182-35/+0
| | | | | | | | | It should be safe for bindings to assume that GPtrArrays hold only pointers (or values as big as it), so there is no need to go through hoops for converting smaller integers when marshalling. Libraries that need arrays of integers should use GArray. https://bugzilla.gnome.org/show_bug.cgi?id=652753
* Allow enums and bitfields to have static methodsTorsten Schönfeld2011-08-163-6/+102
| | | | | | | | | | | | | This uses the same backcompat machinery that was introduced for static methods for non-class types, so this change does not break users of the existing presentations. New libgirepository API: g_enum_info_get_n_methods g_enum_info_get_method https://bugzilla.gnome.org/show_bug.cgi?id=656499
* tests/doctools: Properly clean the temporary mallard filesTomeu Vizoso2011-08-151-1/+4
|
* tests/doctool: Update the -expected dirsTomeu Vizoso2011-08-1516-16/+16
|
* tests/doctool: Make sure we regenerate the mallard code when testingTomeu Vizoso2011-08-151-2/+2
|
* tests/doctool: Better way of copying the .girTomeu Vizoso2011-08-151-6/+6
|
* tests/doctool: Compare -expected directories instead of single filesTomeu Vizoso2011-08-15415-15/+5023
|
* tests/doctool: Switch to test the mallard formatterTomeu Vizoso2011-08-155-3660/+52
|
* tests/doctool: Add the right -expected files to distTomeu Vizoso2011-08-151-1/+1
|
* tests/doctool: Update expected filesTomeu Vizoso2011-08-152-77/+161
|
* g-ir-doc-tool: Use namespace.class for PythonTomeu Vizoso2011-08-151-26/+26
|
* g-ir-doc-tool: Add -expected test for Python docbookTomeu Vizoso2011-08-153-6/+1793
|
* Regress-1.0-expected: Update for previous changeColin Walters2011-08-151-0/+40
|
* annotationparser: Don't eat lines that look like parameters outside param listColin Walters2011-08-142-0/+39
| | | | | | | | | If we're done parsing parameters, previously we would simply eat lines that looked like @foo: blah blah Example is in gtkcssprovider.c. https://bugzilla.gnome.org/show_bug.cgi?id=656504
* Merge remote-tracking branch 'origin/gir-docbook'Johan Dahlin2011-08-133-1/+1802
|\ | | | | | | | | | | Conflicts: .gitignore tests/scanner/Regress-1.0-expected.gir
| * tests/doctool: Updated -expected to match the code in the repoTomeu Vizoso2011-08-131-62/+6
| |
| * g-ir-doc-tool: Add alias elements (typedef)Tomeu Vizoso2011-08-131-11/+451
| |
| * Add signal flagsJohan Dahlin2011-08-134-10/+70
| | | | | | | | | | | | This adds all GSignalFlags into the gir. https://bugzilla.gnome.org/show_bug.cgi?id=656457
| * Update expected after rebaseJohan Dahlin2011-08-131-6/+62
| |
| * Move doctool over to common.mkJohan Dahlin2011-08-131-1/+1
| |
| * scanner: Don't throw away blank lines in the docsColin Walters2011-08-133-0/+31
| | | | | | | | | | | | For generating documentation, we actually want to preserve these. https://bugzilla.gnome.org/show_bug.cgi?id=656389
| * Add g_irepository_find_by_error_domain()Dan Winship2011-08-131-0/+9
| | | | | | | | | | | | | | | | Add a method to look up a GIEnumInfo given its associated error quark. Based on a patch from Colin Walters. https://bugzilla.gnome.org/show_bug.cgi?id=602516
| * Switch to storing string form of error quarksDan Winship2011-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of storing the name of the function to call to get the error quark, store the string form of the error quark, which we derive from the introspection binary during scanning. Update EnumBlob and GIEnumInfo to include the new information. This will allow determining a back-mapping from error quark to error domain without having to dlsym() and call all the known error quark functions. Based on earlier patches from Owen Taylor and Maxim Ermilov. https://bugzilla.gnome.org/show_bug.cgi?id=602516
| * Add Regress method for a closure taking and returning a GVariantMartin Pitt2011-08-133-0/+50
| |
| * g-ir-doc-tool: Use same link ids as gtk-doc-mkdb doesTomeu Vizoso2011-08-131-104/+104
| |
| * g-ir-doc-tool: Move out the * from the return value linkTomeu Vizoso2011-08-131-40/+40
| |
| * g-ir-doc-tool: Move the * out the type linkTomeu Vizoso2011-08-131-106/+106
| |
| * g-ir-doctool: Add annotations (some)Tomeu Vizoso2011-08-121-0/+20
| |
| * g-ir-doc-tool: Generate parameter list in the detailTomeu Vizoso2011-08-121-0/+785
| |
| * tests/doctool: use GIRepository gir instead of RegressTomeu Vizoso2011-08-123-752/+539
| |
| * g-ir-doc-tool: Add DOCTYPETomeu Vizoso2011-08-111-0/+5
| |