| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Code uses LOG_COMPILER, comment mistakenly still
mentioned TESTS_ENVIRONMENT.
|
|
|
|
|
| |
we already go through 'env' for all other TESTS_ENVIRONMENT
statements, reason to not do so here too...
|
|
|
|
|
| |
"--warn-all --reparse-validate" is already contained in
$(INTROSPECTION_SCANNER_ARGS), no need to repeat
|
|
|
|
|
|
| |
02e545371e2132a97458888895cacf57b8c0f83a (2015-06-23)
https://bugzilla.gnome.org/show_bug.cgi?id=725685
|
|
|
|
|
|
|
|
|
|
| |
"cairo-1.0.gir" is generated into "$(top_builddir)/gir" but
g-ir-scanner is never instructed to look into that directory.
This fails somewhat when there is no system installed copy
of it when VPATH building "tests/scanner/Regress-1.0.gir":
Couldn't find include cairo-1.0.gir (search path: "everything except the correct value")
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
|
| |
Adding "$(top_srcdir)/gir" to XDG_DATA_DIRS is pointless
as scanner/transformer.py actually goes looking for
"$(top_srcdir)/gir/gir-1.0", which doesn't exist.
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
42bb69a6a2f12165a9758b192e80da089e00ab5c introduced a bug causing
test_parser.py and test_patterns.py tests to be executed twice.
This patch fixes this and still allows the tests to be executed:
- using 'make check'
- manually:
PYTHONPATH=. python tests/scanner/annotationparser/test_parser.py
PYTHONPATH=. python tests/scanner/annotationparser/test_patterns.py
- individually:
python -m unittest test_parser.TestGiTag_Stability.test_001
python -m unittest test_patterns.TestCommentAsterisk.test_000
test_parser.py now results in:
Ran 360 tests in 0.172s
instead of:
Ran 720 tests in 0.339s
test_patterns.py now results in:
Ran 213 tests in 0.014s
instead of
Ran 426 tests in 0.041s
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
| |
libfoo was moved into libregress in 9fc6eb16e954559d97cdd9a03437c8b1877c2a1d
libtestinherit was moved into libregress in bb1ac9cf2dc450c5d44b1e39e3162ba06069f4a1
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
|
| |
tests/scanner/annotationparser/test_[parser|patterns].py
stopped working with Python3 somewhere down the line due
to the iteritems() call...
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
|
|
|
|
| |
Generalize "throws" attribute to SignatureBlob which can be used by all
callable blob types. Keep FunctionBlob and VFuncBlob throw attributes
around and functional for compatibility. Refactor girwriter.c to write
out throws attribute for all callable types.
Based on a patch by Simon Feltman.
https://bugzilla.gnome.org/show_bug.cgi?id=729543
|
|
|
|
| |
Based on a patch by Simon Feltman.
|
|
|
|
|
|
|
|
|
|
|
| |
Add find_field utility function for finding a field info by name.
Beyond convenience, this should be faster than manually using
the get_n_fields and get_field functions because get_field does
an additional iteration for each field to calculate offsets O(n^2).
Thus find_field combines the offset and comparison
computations into a single loop O(n).
Based on a patch by Simon Feltman.
|
|
|
|
|
| |
Add missing doc-tool tests, fixes "make distcheck" breakage
introduced by 09daa28c5b4625b6f274b3b340bc85e33bef80b5
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751150
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750286
|
|
|
|
|
|
|
|
|
|
| |
Add the command line flag --symbol-filter-cmd to g-ir-scanner
which allows running symbol names through a filtering shell
command. The symbol is sent as stdin to the filter command
and expects a filtered result written to stdout.
https://bugzilla.gnome.org/show_bug.cgi?id=744534
Signed-off-by: Garrett Regier <garrett.regier@riftio.com>
|
|
|
|
|
|
|
| |
Allow `identifier`, `parameter` and `tag` part `annotations` fields
to span multiple lines
https://bugzilla.gnome.org/show_bug.cgi?id=676133
|
|
|
|
|
|
| |
Extends commit 92d9c38 to also pass CC to g-ir-scanner.
https://bugzilla.gnome.org/show_bug.cgi?id=700066
|
|
|
|
|
|
|
|
|
|
| |
Doing so reveals GIRParser did not yet support:
- the (skip) annotation on parameters and return values
- the (attributes) annotation
This patch fixes both issues an prevents further similar problems.
https://bugzilla.gnome.org/show_bug.cgi?id=738171
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
What we already had:
- (array zero-terminated=1) > array which is NULL terminated
- (array zero-terminated=0) > array which is not NULL terminated
- (array) > array which is not NULL terminated
- (array zero-terminated=X) > array which is not NULL terminated
where X can be anything
What this patch adds:
- (array zero-terminated) > array which is NULL terminated
https://bugzilla.gnome.org/show_bug.cgi?id=657754
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=738989
|
|
|
|
|
|
|
| |
This is an installed file, so we can't assume that config.h
will be around.
https://bugzilla.gnome.org/show_bug.cgi?id=737275
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RegressIntSet and RegressIntset, aliases of one another, were causing
two documentation pages to be built by the documentation tests that
were named identically except for letter case.
On OSX and Windows, the most common filesystems are case-insensitive,
and those two files can't exist in the same directory on case-
insensitive filesystems. That caused the tests to fail. It also caused
problems when checking out the repository, because the expected
documentation set also contains those files.
This commit fixes the symptom (so that JHbuild will stop erroring out
on this module) but not the problem of generating a documentation set
for two identifiers which differ (perfectly legally) only by case.
https://bugzilla.gnome.org/show_bug.cgi?id=725264
|
|
|
|
|
|
|
|
|
| |
We have special code to look at (type GLib.List(utf8)), but (type
GLib.PtrArray(utf8)) didn't work.
This allows NetworkManager to annotate the ActiveConnections property.
https://bugzilla.gnome.org/show_bug.cgi?id=733879
|
|
|
|
|
|
|
|
|
| |
Make use of the new options in codegen.py/testcodegen.py so that the
symbols in the generated everything.[c|h] can be annotated for export, and
the necessary headers to facilitate the compile-time symbol exporting can
be included appropriately.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
|
|
| |
Like the other test programs, include config.h before anything and decorate
the lone symbols for export, and include $(top_srcdir)/tests so that
gitestmacros.h can be found and used.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
|
| |
The annotation for gi_marshalling_tests_object_int8_out used the wrong
function name, causing the annotation not to be picked up.
https://bugzilla.gnome.org/show_bug.cgi?id=727665
|
|
|
|
|
|
|
|
|
|
|
| |
Use compiler directives for exporting symbols for the build of
libgirepository and also for the test libraries, like what is now done
in GLib and GTK+ so that maintaining a separate .symbols (and .def files)
would not be needed, in which the correct compiler directive is determined
during configure time. Drop all the .def files and the .symbols file as
we would not be using them anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
|
|
|
|
| |
This updates the test headers and sources to decorate the symbols with the
macro that can be used to export the symbols, and include config.h first in
the c-sources so that the macro can be defined with the compiler directive
to export the symbols. Update the CFLAGS as well so that the header that
defines the export decoration macro can be found.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
|
|
|
| |
This updates the test headers and sources to decorate the symbols with the
macro that can be used to export the symbols, and include config.h first in
the c-sources so that the macro can be defined with the compiler directive
to export the symbols.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
|
|
|
|
| |
This adds a header under tests/ that can be included by the various test
libraries/sources so that symbols from them can be decorated by a macro,
which can then be used to export symbols by using a compiler directive,
like the updates to girepository. This header is also installed as the
test headers refer to them.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
|
| |
unistd.h is not universally available, and dropping that include did not
seem to cause any warnings or errors, and did not affect the tests running.
https://bugzilla.gnome.org/show_bug.cgi?id=734640
|
|
|
|
|
|
| |
Update based additional test added with commit e2b96aaa4
https://bugzilla.gnome.org/show_bug.cgi?id=702508
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702508
|
|
|
|
|
|
| |
Make sure a constructor that sets a GError works correctly.
https://bugzilla.gnome.org/show_bug.cgi?id=727004
|
|
|
|
|
|
|
|
|
|
|
| |
Knowing the ownership transfer for instance parameters is
necessary for correct memory management of functions which
"eat" their instance argument, such as g_dbus_method_invocation_return_*.
Parse this information from the gir file and store in the
typelib, and then provide new API on GICallableInfo to
retrieve this.
https://bugzilla.gnome.org/show_bug.cgi?id=729662
|
|
|
|
|
| |
Add missing identfilter.py to EXTRA_DIST and correct spelling of
Identfilter-1.0-expected.gir.
|
|
|
|
|
|
|
|
|
| |
Add the command line flag --identifier-filter-cmd to g-ir-scanner which
allows running identifier names through a filtering shell command. The
identifier is sent as stdin to the filter command and expects a filtered
result written to stdout.
https://bugzilla.gnome.org/show_bug.cgi?706898
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=728409
|
|
|
|
|
| |
Now that Cancellable and AsyncReadyCallback are being correctly
recognised again, adjust the expected output of the Regress testcase.
|
|
|
|
|
|
|
| |
This reverts commit 0839e696e9fbc1942ac5c61054de3b47e9578152.
This was accidentally picked up by my 'git bz apply' against the bug as
I was getting ready to push the last set of changes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Record our internal 'nullable' and 'optional' attributes into the
written .gir file. It is now theoretically possible to express the
concept of an out parameter with a nullable type (although presently
there is no way to do this).
Modify our own internal parser (in the scanner) to understand the
newly-written attributes.
Update the expected output of the 'Regress-1.0.gir' test to account for
the new attributes.
Nothing else understands 'nullable' yet, but the girparser in the
typelib compiler already understands 'optional' and records a bit for it
in the typelib.
https://bugzilla.gnome.org/show_bug.cgi?id=660879
|
|
|
|
|
|
|
|
|
| |
The old annotationparser.py happily parsed this, but
giscanner/girwriter.py never serialized an allow-none
attribute to the .gir file and girepository/girparser.c
never looked for an allow-none attribute either.
https://bugzilla.gnome.org/show_bug.cgi?id=660879
|
|
|
|
|
|
|
| |
The implementation as a method returning itself as its implemented
interface type.
https://bugzilla.gnome.org/show_bug.cgi?id=727824
|
| |
|
|
|
|
|
| |
This was causing a "warning: function declaration isn't a
prototype" with strict-prototypes enabled.
|
|
|
|
|
|
| |
Add missing page needed for tests to run after commit 7027bb256
https://bugzilla.gnome.org/show_bug.cgi?id=725198
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use ParseState enum instead of a boolean for the ParseContexts embedded_type
flag. This allows specific tracking of the embedded type currently being
parsed which can now either be STATE_STRUCT_FIELD or STATE_CLASS_FIELD (or
allow for future expansion). Add ParseState::STATE_NONE as the default for
this field.
Fix GObject FieldBlob validation to take into account the sizeof
CallbackBlobs (copied from the struct validator).
Add static g_object_info_get_field_offset which parallels
g_struct_info_get_field_offset which is needed since callback fields may
vary in size.
https://bugzilla.gnome.org/show_bug.cgi?id=725198
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
a final underscore
In cases like g_resources_register() and gdk_events_get_angle(),
the c_symbol_prefix of the first parameter (resp. g_resource and
gdk_event) is a prefix of the symbol, but the next character is
not _, so that should not be considered a method.
For backward compatibility reasons, we still generate one, but
then it's not included in the documentation (because of moved_to)
|