summaryrefslogtreecommitdiff
path: root/giscanner
Commit message (Collapse)AuthorAgeFilesLines
* giscanner: fix use after decrefAndreas Schwab2011-12-151-4/+6
| | | | | Decrement reference to temporary string object only after last use of its value.
* scanner: Put the -l library names after the .oAlbert Astals Cid2011-11-291-5/+5
| | | | | | | | | | | | | | | | That is how gcc expects them. From the gcc man page: -llibrary Search the library named library when linking. It makes a difference where in the command you write this option; the linker searches and processes libraries and object files in the order they are specified. Thus, foo.o -lz bar.o searches library z after file foo.o but before bar.o. If bar.o refers to functions in z, those functions may not be loaded. https://bugzilla.gnome.org/show_bug.cgi?id=664616
* Add a floating alias for noneJohan Dahlin2011-11-252-4/+13
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=657202
* giscanner: Add gmodule-2.0 to compiler packagesFlorian Müllner2011-11-231-1/+1
| | | | | | | Gio no longer draws in gmodule, so we need to add the dependency explicitly. https://bugzilla.gnome.org/show_bug.cgi?id=664681
* OpenBSD uses it's own libtool implementation which breaks giscanner in certainJasper Lievisse Adriaanse2011-11-181-0/+14
| | | | | | situations. So adjust resolve_non_libtool() in this case. https://bugzilla.gnome.org/show_bug.cgi?id=664282
* scanner: Only add rpaths for absolute directoriesColin Walters2011-11-031-5/+6
| | | | | We shouldn't do it for module-internal paths, since it can't work and is unnecessary even if it did.
* scanner: Also add an RPATH for library paths specifiedColin Walters2011-11-031-0/+5
| | | | | | | | | | | Introspection scanning is a bit special in that we both compile *and* run a temporary binary. In some cases like jhbuild we will pick up the runtime location of libraries via LD_LIBRARY_PATH. But this falls over when we've been given a private subdirectory, since it won't be in that path. Let's just "do the right thing" here by injecting an rpath for the directories as well.
* Windows port: fix _resolve_non_libtoolDieter Verfaillie2011-10-201-25/+32
| | | | | | By simply appending '.dll' to the library names. https://bugzilla.gnome.org/show_bug.cgi?id=620566
* scanner: Support --header-only flagColin Walters2011-10-191-2/+10
| | | | | This is useful for someone who just wants a set of constants from a .h file accessible by introspection.
* message: Show the file/line even when processing FATALColin Walters2011-10-171-5/+5
| | | | This helps debug. Also, add a 'fatal' debug break.
* scanner: allow GObject.Object as a superclass return typeDan Winship2011-10-131-1/+1
| | | | | | | 6172c268 made the scanner think GObject* wasn't a superclass of its subclasses. Fix that. https://bugzilla.gnome.org/show_bug.cgi?id=661677
* dumper: Don't call g_thread_init(), g_type_init() is enoughColin Walters2011-10-121-1/+0
| | | | g_thread_init() is deprecated, and unnecessary since GLib 2.24.
* scanner: split CC environment variableNatanael Copa2011-10-101-1/+2
| | | | | | | | This fixes compilation where CC="ccache gcc" and similar. https://bugzilla.gnome.org/show_bug.cgi?id=660160 Signed-off-by: Natanael Copa <ncopa@alpinelinux.org>
* Skip analysis of params that have been (skip)'dStef Walter2011-09-281-0/+3
| | | | | | Otherwise we get warnings for params that have been skipped https://bugzilla.gnome.org/show_bug.cgi?id=660352
* Fix incorrect extension for tempfileDieter Verfaillie2011-09-191-1/+1
| | | | | | | | | | | | | I set ext to None in commit f2a70843905839a1b11795310d2aa3b85a474e77 without realizing _generate_tempfile does a simple string formatting. A simple test proves this does not generate an empty string: $ python -c "f = '%s' % None; print f, type(f)" None <type 'str'> So pass an empty string instead of None for the suffix parameter. https://bugzilla.gnome.org/show_bug.cgi?id=659502
* Add constant value annotationJohan Dahlin2011-09-146-7/+24
| | | | | Add an annotation tag "Value:" which can be used on constants to override the value.
* scanner: Don't add redundant notify signalColin Walters2011-09-121-4/+0
| | | | It was actually introduced by e0fea819f0da1ca60cce3280e7e21f3d2955be3a
* scanner: Only add notify signal to Object, not ParamSpec etc.Colin Walters2011-09-121-3/+4
|
* scanner: correctly handle structs with arrays of anon unionsTorsten Schönfeld2011-09-111-11/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/+3
| | | | | 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: g-ir-scanner: Accept -m flagsDieter Verfaillie2011-09-071-0/+12
| | | | | | | | Some pkgconfig files contain these flags on Windows, for example gtk+-3.0.pc has -mms-bitfields in it's Cflags. Nothing is done yet with these though, we only accept these flags for now... https://bugzilla.gnome.org/show_bug.cgi?id=620566
* Windows port: Export all symbols on Windows.Dieter Verfaillie2011-09-071-1/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=620566
* Windows port: the tmpfile is going to be an exe...Dieter Verfaillie2011-09-071-1/+7
| | | | | | ... on Windows, so take care of the extension. https://bugzilla.gnome.org/show_bug.cgi?id=620566
* Windows port: Do not append '/usr/share' to _xdg_data_dirs...Dieter Verfaillie2011-09-071-2/+6
| | | | | | | ... on Windows as it points to the MinGW installation directory, which doesn't have any .gir files to start with anyway. https://bugzilla.gnome.org/show_bug.cgi?id=620566
* Let the user override the default compiler with the CC env variableAndoni Morales Alastruey2011-09-031-1/+1
|
* Fix compilation with mingwAndoni Morales Alastruey2011-09-032-1/+11
| | | | | | grealpath.h defines GetFullPathNameA() as windows.h is not imported, but for gitscanner.c, windows.h is imported and the compiler throws an error.
* scanner: Don't try to copy c:type if we're parsing (element-type)Colin Walters2011-08-291-5/+10
| | | | | | | | | | | | | 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
* scanner: Remove some dead debugging codeColin Walters2011-08-291-3/+0
|
* Fix warning for missing (element-type)Colin Walters2011-08-291-2/+2
| | | | | | 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.
* Avoid most of the special-casing of GObject.Object in the scannerPavel Holejsovsky2011-08-281-48/+14
| | | | | | | | | There were some cases of handling GObject and GInitiallyUnowned which were not necessary. Removing special cases from them simplified code and as a bonus it added 'GObject::notify' signal into GIR, which was not there previously. https://bugzilla.gnome.org/show_bug.cgi?id=657446
* 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
* docbookdescription.py: Fix for PEP-8 complianceColin Walters2011-08-221-3/+3
|
* Add tests for newly added warningsGiovanni Campagna2011-08-181-3/+3
| | | | | g-ir-scanner now warns for invalid (element-type) annotations in GPtrArray and in GByteArray. Test that.
* Disallow non byte types for GByteArraysGiovanni Campagna2011-08-181-2/+14
| | | | | | | | | 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-0/+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-164-1/+18
| | | | | | | | | | | | | 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
|
* [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
|
* output namespace.class.methodname for python methods in the doctoolsJohn (J5) Palmieri2011-08-151-1/+1
|
* fix up Python doc backend to output correct namesJohn (J5) Palmieri2011-08-151-3/+3
|
* first pass at python backend for doc toolsJohn (J5) Palmieri2011-08-151-1/+11
|
* 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
|
View Lorry Controller Status