summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* Revert "xlib: fix the type of XID"Giovanni Campagna2011-08-261-14/+18
| | | | | | | This reverts commit 3553cd0a4631f1b57fb608e3f3f78a1a0cfd602a. Turns out it was wrong, XID is 64 bit on a 64 bit system. Plus the scanner doesn't like multiple level typedefs.
* xlib: fix the type of XIDGiovanni Campagna2011-08-261-18/+14
| | | | | | | | XIDs are CARD32, which corresponds to guint32 on all platform, not gulong (which is 64 bit on x86_64). Fix that, and use alias indirection to more accurately reflect the typedefs. https://bugzilla.gnome.org/show_bug.cgi?id=643620
* configure.ac: Do not generate template filesJavier Jardón2011-08-261-1/+1
| | | | | It's not needed as the project uses inline comments for documentation.
* configure.ac: Generate xz tarball with ustar format by defaultJavier Jardón2011-08-261-2/+2
|
* Update autotools configurationJavier Jardón2011-08-262-11/+19
| | | | | Replace deprecated autoconf macros Use new libtool syntax
* autogen.sh: Use autoreconf instead custom scriptJavier Jardón2011-08-261-37/+18
|
* Fix g_irepository_find_by_gtype() for GDK_TYPE_RECTANGLEPavel Holejsovsky2011-08-251-0/+11
| | | | | | | | | | | | | | | | | | Complement fix for g-ir-scanner which converts every GdkRectangle gtype to CairoRectangleInt. Make sure that C-side API is also aware of this workaround. Use case requiring this patch: When binding implementation wants to get/set property, it can use either GI-based approach (g_property_info_xxx() funcs), or just GLib facilities. Although former is probably preferred, there are cases when latter is still needed (e.g. gstreamer uses dynamic properties, which are not present in the gir). In this case, binding implementation queries the type of the propertyb (using g_object_class_find_property()), it gets GDK_TYPE_RECTANGLE, and without the patch it cannot map it to any known type. https://bugzilla.gnome.org/show_bug.cgi?id=655423
* Properly handle GParamSpec and descendantsPavel Holejsovsky2011-08-251-6/+21
| | | | | | | GParamSpec is introspected as fundamental class, and all GObject classes derived from it (e.g. GParamSpecChar) are marked as such. https://bugzilla.gnome.org/show_bug.cgi?id=656440
* Update annotations from glib git 2cd3c200687751c9cc26774f650b7651bffcc598Jasper St. Pierre2011-08-242-21/+24
|
* Remove MAINTAINERS and add DOAPJasper St. Pierre2011-08-242-7/+46
|
* 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.
* docbookdescription.py: Fix for PEP-8 complianceColin Walters2011-08-221-3/+3
|
* Update annotations from glib git d51e0615f9a6c1aa1898c46f2cf3135ca5ccd463Colin Walters2011-08-223-133/+83
|
* Add 'Since:' tags to the newly added GIEnumInfo methodsTorsten Schönfeld2011-08-181-0/+4
|
* Regenerate Gio/GLib/GObject annotationsMartin Pitt2011-08-183-401/+6099
| | | | Ran misc/update-glib-annotations.py against current glib master.
* Add tests for newly added warningsGiovanni Campagna2011-08-182-4/+30
| | | | | 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-182-3/+15
| | | | | | | | | 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-184-35/+18
| | | | | | | | | 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
* Docbookwriter: signal flagsLaszlo Pandy2011-08-171-1/+18
|
* In DocBookWriter, remove DocBookEntity and just use the ast nodes directly.Laszlo Pandy2011-08-171-73/+39
|
* For docbook, make the id attributes the same regardless of language. Only ↵Laszlo Pandy2011-08-161-10/+5
| | | | user visible strings should change between C and Python.
* Descriptions support for docbook writer.Laszlo Pandy2011-08-162-18/+199
| | | | | | Includes support for escaping (but not double escaping) entities and CDATA sections. Add descriptions from GIR to docbook writer.
* Allow enums and bitfields to have static methodsTorsten Schönfeld2011-08-1615-17/+237
| | | | | | | | | | | | | 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
* Teach scanner's girparser about fundamentalsPavel Holejsovsky2011-08-161-0/+8
| | | | | | | Make sure that fundamental attribute and associated functions (ref-func, unref-func, set-value-func and get-value-func) are parsed, otherwise we fail reparse-validating girs containing fundamentals.
* giscanner: Allow passing additional include dirs when parsing a girTomeu Vizoso2011-08-152-2/+11
|
* 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
|
* [doctools] use 'or' instead of 'and' when checking for func or constructorJohn (J5) Palmieri2011-08-151-1/+1
|
* treat constructors like methods when generating the labelJohn (J5) Palmieri2011-08-151-1/+1
|
* [doctool] use different templates for method vs. function outputJohn (J5) Palmieri2011-08-151-1/+4
|
* configure.ac: Change to tar-ustar because PAX gives problems in OpenBSDTomeu Vizoso2011-08-151-1/+1
| | | | Also, it's what other GNOME modules use
* tests/doctool: Better way of copying the .girTomeu Vizoso2011-08-151-6/+6
|
* configure.ac: Add tar-pax to AM_INIT_AUTOMAKETomeu Vizoso2011-08-151-1/+1
|
* output namespace.class.methodname for python methods in the doctoolsJohn (J5) Palmieri2011-08-151-1/+1
|
* tests/doctool: Compare -expected directories instead of single filesTomeu Vizoso2011-08-15415-15/+5023
|
* fix up Python doc backend to output correct namesJohn (J5) Palmieri2011-08-151-3/+3
|
* tests/doctool: Switch to test the mallard formatterTomeu Vizoso2011-08-155-3660/+52
|
* first pass at python backend for doc toolsJohn (J5) Palmieri2011-08-151-1/+11
|
* 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: Fix PEP-8 issuesTomeu Vizoso2011-08-151-11/+7
|
* g-ir-doc-tool: print class declaration line in PythonTomeu Vizoso2011-08-151-14/+40
|
* giscanner/mallardwriter: Adding experimental Mallard output to g-ir-doc-toolShaun McCance2011-08-154-8/+495
|
* g-ir-doc-tool: Use namespace.class for PythonTomeu Vizoso2011-08-152-27/+33
|
View Lorry Controller Status