summaryrefslogtreecommitdiff
path: root/giscanner
Commit message (Collapse)AuthorAgeFilesLines
* scanner: Fall back to default uscoring for method pairing if possibleColin Walters2010-11-161-6/+16
| | | | | | The commit to use the c_symbol_prefix works in every case, except for gdk_window_object_get_type(), which screws us. Fall back to the old heuristic in this case.
* Fix line too longColin Walters2010-11-161-1/+2
|
* scanner: use c-symbol-prefix for method pairing where possibleJonathan Matthew2010-11-161-1/+4
| | | | | | | | | If we have a C symbol prefix for the target type, then use that to identify methods that should be paired with it. The C symbol prefix is derived from the name of the _get_type() function, so it's likely that this is also the prefix given to methods for the type. https://bugzilla.gnome.org/show_bug.cgi?id=634153
* scanner: don't show 'warnings suppressed' if --warn-all in useJonathan Matthew2010-11-161-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=633227
* Add support for gunichar in typelibColin Walters2010-11-121-4/+0
| | | | | | | Some API such as gtk_text_iter_get_char returns an individual "gunichar"; we should support this. https://bugzilla.gnome.org/show_bug.cgi?id=633197
* dumper: Differentiate between "external" and "internal" linkingColin Walters2010-11-112-12/+37
| | | | | | | | | | | The previous commit aea515709 broke scanning for libraries not in the current directory, such as scanning Gio from gobject-introspection. In this case, it's wrong to add -L., and to move the other -L behind the library. Instead, we should just do a "normal" link using pkg-config --libs with few games. https://bugzilla.gnome.org/show_bug.cgi?id=632701
* Switch to nonrecursive make for core (i.e. not tests/)Colin Walters2010-11-094-93/+21
| | | | | This is cleaner and faster, and prepares us better for an incoming import of CMPH.
* libtoolimporter: Don't assume we have a multi-component importColin Walters2010-11-091-2/+6
| | | | | os.path.join barfs if we're passing it 0 arguments, as would happen when doing "import foo".
* Handle enumerations with the full range of signed and unsigned valuesOwen W. Taylor2010-11-014-12/+31
| | | | | | | | | | | | | The C compiler will pick an enumeration type that accomodates the specified values for the enumeration, so ignoring 64-bit enumerations, we can have enumeration values from MININT32 to MAXUINT32. To handle this properly: - Use gint64 for holding eumeration values when scanning - Add a 'unsigned_value' bit to ValueBlob so we can distinguish the int32 vs. uint32 cases in the typelib - Change the return value of g_value_info_get_value() to gint64. https://bugzilla.gnome.org/show_bug.cgi?id=629704
* scanner: Print out a message if warnings were offColin Walters2010-10-252-6/+10
| | | | | | Otherwise people may not know about --warn-all. https://bugzilla.gnome.org/show_bug.cgi?id=631644
* Fix previous commitColin Walters2010-10-221-1/+1
|
* Handle CC="ccache gcc" for linker command tooColin Walters2010-10-221-1/+2
| | | | | The compiler path explicitly split()s the variable, we should do so in the linker path too.
* scanner: Support GStrv as signal parametersColin Walters2010-10-211-0/+5
|
* scanner: Don't process pkg-config libs twiceColin Walters2010-10-192-13/+3
| | | | | | | | | | | | Before, we were adding the --libs-only-L from pkg-config files during initial scanning, as if --library-path was specified, *and* inside the dumper, we used --libs. Fix this by always doing -L. <introspected libraries> <pkg-config libs> This should ensure we don't duplicate the search path anyways. https://bugzilla.gnome.org/show_bug.cgi?id=631348
* Accept trailing whitespace at the start of a comment blockColin Walters2010-10-191-5/+3
| | | | | | Might as well be liberal here, as long as we have a test case. https://bugzilla.gnome.org/show_bug.cgi?id=631690
* scanner: Don't leave temporary directory around if we failColin Walters2010-10-072-17/+30
| | | | | ...by default. However, the GI_SCANNER_DEBUG=save-temps option helps for debugging.
* Revert "Apply `(type bitfield)' annotations for enums"Johan Dahlin2010-10-061-9/+2
| | | | This reverts commit d15e386c8e10dd6b645a444e29cc053100089a07.
* Revert "block can be None, fixup last commit"Johan Dahlin2010-10-061-4/+3
| | | | This reverts commit 754e5462f6dfbe3793eb959abf3dbfa7d2fe6435.
* chose extension basing on OSAlexey Zakhlestin2010-10-061-2/+11
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=606686
* block can be None, fixup last commitJohan Dahlin2010-10-051-3/+4
|
* Apply `(type bitfield)' annotations for enumsAndreas Rottmann2010-10-051-2/+9
| | | | Previously, such annotations would be ignored.
* Silently skip #pragma directives when scanning sources.Pavel Holejsovsky2010-10-031-0/+1
| | | | | | | This is useful e.g. on cygwin, where system headers use #pragma directives, causing annoying false-alarm errors during every g-ir-scanner run. https://bugzilla.gnome.org/show_bug.cgi?id=630994
* Honor -L commandline option.Pavel Holejsovsky2010-10-031-0/+3
|
* Add -export-dynamic when compiling with libtoolOwen W. Taylor2010-09-301-0/+2
| | | | | | In some cases (such as introspecting a convenience library), we need to dlsym() modules in the binary we compile, so we need to add -export-dynamic to the link line.
* scanner: Don't link to -lgirepository when dumpingGOBJECT_INTROSPECTION_0_9_9Colin Walters2010-09-301-38/+25
| | | | | | | | This helps us avoid a problematic case where in say jhbuild, using a system (/usr/lib) glib, adding in -l girepository-1.0 will inject -L /path/to/builddir, when we don't want that. https://bugzilla.gnome.org/show_bug.cgi?id=630342
* scanner: Abort if we would be generating an empty namespaceColin Walters2010-09-291-0/+6
| | | | | | | | | Kind of silly we weren't doing this before; an empty namespace is always going to be unintentional. The "oops I forgot to include .h" files actually happened with Clutter, but it wasn't caught since the build didn't obviously fail.
* scanner: Don't duplicate fatal message textColin Walters2010-09-291-1/+2
|
* annotationparser: Don't ignore annotations if there's a : in docsGOBJECT_INTROSPECTION_0_9_8Colin Walters2010-09-281-1/+5
| | | | | | | | The annotation parser changed to be stricter about annotation content, but we introduced a regression where a : in the documentation would wrongly cause the annotation to be skipped. https://bugzilla.gnome.org/show_bug.cgi?id=630862
* Fix --include-uninstalledColin Walters2010-09-281-3/+3
| | | | | Somehow, this regressed; i have no idea how. We need to be comparing Include objects, not string versus Include.
* scanner: fail if cpp failsVincent Untz2010-09-271-0/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=630101
* [scanner] Make sure private enums are filteredJohan Dahlin2010-09-262-2/+4
| | | | This is a follow-up to 60a8c75 which wasn't properly fixed.
* Remove trailing whitespaceJohan Dahlin2010-09-262-34/+34
|
* [scanner] Mark enum members as private in transformerJohan Dahlin2010-09-262-9/+3
| | | | | | | Remove enum members which follows /* <private> */ comments inside the transformer instead of the sourcescanner itself. Fixes a crash when creating the gir for GstBase.
* [sourcescanner] Plug a couple of python leaksJohan Dahlin2010-09-261-4/+1
| | | | | There's no need to increase the reference count to items passed into PyList_SetItem, it already steals a reference.
* [annotationparser] Extract (skip) for doc blocksJohan Dahlin2010-09-251-1/+8
|
* Setup message loggerJohan Dahlin2010-09-241-0/+3
| | | | Since the annotationparser may warn
* Print out line numbersJohan Dahlin2010-09-241-3/+7
| | | | | But disable the printing by default since it messes up the generated file. And fix a couple of typos
* Use tag position if availableJohan Dahlin2010-09-241-0/+6
|
* [girparser] Callbacks and VFunctions can be shadowedJohan Dahlin2010-09-241-2/+3
|
* Add a script to extract gio annotationsJohan Dahlin2010-09-243-17/+17
|
* Add an annotation toolJohan Dahlin2010-09-243-0/+131
|
* [scannermain] Split scanner_main into smaller piecesJohan Dahlin2010-09-241-89/+115
| | | | | Split it into pieces that will be reusable across different command line tools.
* [annotationparser] Allow param less closuresJohan Dahlin2010-09-242-2/+6
| | | | | Allow closures without annotations to avoid having to duplicate the parameter name.
* Add more array warnings + testsJohan Dahlin2010-09-242-6/+30
|
* [annotationparser] Validate the rest of the annotationsJohan Dahlin2010-09-241-19/+87
| | | | | All option annotations, which uses parenthesis are now properly validated for number of values they expect
* [maintransformer] Add more warnings for element-typeJohan Dahlin2010-09-241-5/+28
|
* [maintransformer] Use constantsJohan Dahlin2010-09-241-3/+3
|
* Add a position to doc optionsJohan Dahlin2010-09-241-2/+8
|
* [annotation] Add constants for out optionsJohan Dahlin2010-09-242-2/+7
|
* [maintransformer] Use AssertionErrorJohan Dahlin2010-09-241-5/+2
|