| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... in the projects for now, the NMake Makefiles for the introspection files
(.gir/.typelib) need to be updated as well, but that needs to be done a bit
later.
This is done by updating the autotools scripts, so that the Visual Studio
2010 projects are copied and the items are updated as necessary.
Note that since the format of the platform toolset changed for Visual Studio
2017, a custom platform toolset string is allowed and used if specified,
otherwise the platform toolset string is generated as it was before.
|
| |
|
| |
|
|
|
|
|
|
| |
As suggested, we don't really need two layers of directories to get to the
projects, so move the project files to be under win32/ rather than
build/win32/.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is used for generating the pkg-config file for this package.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 98bb6c91b710a95efe4cfeb303daeec3381b9c98.
It breaks programs simply executed *transitively* from a setuid
binary like the dbus daemon launch helper.
https://bugzilla.redhat.com/show_bug.cgi?id=1285991
Conflicts:
girepository/girepository.c
|
| |
|
|
|
|
|
|
|
| |
Add --with-python flag which overrides the $PYTHON environment
variable when used.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
|
| |
Update the common autotools module that was used to create the
Visual Studio 2012/2013 projects so that we can create the 2015
projects as well. The 2015 projects, like the 2012 and 2013 ones
are largely similar to the 2010 ones in format, so we just need to
copy the 2010 projects and replace the items in there as needed.
|
|
|
|
|
|
|
|
| |
We know of at least one privilege escalation path via
`GI_TYPELIB_PATH`. I don't want to audit for others. If someone
shows up with a use case we can talk.
https://bugzilla.gnome.org/show_bug.cgi?id=755472
|
| |
|
| |
|
| |
|
|
|
|
| |
optparse is deprecated.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
g-i bug reports have been moved from:
http://bugzilla.gnome.org/enter_bug.cgi?product=glib&component=introspection
to:
http://bugzilla.gnome.org/enter_bug.cgi?product=gobject-introspection
https://bugzilla.gnome.org/show_bug.cgi?id=745498
|
| |
|
|
|
|
|
|
| |
The executable is named 'g-ir-doc-tool', not 'g-ir-doctool'.
https://bugzilla.gnome.org/show_bug.cgi?id=670985
|
|
|
|
|
|
| |
during autoreconf"
This reverts commit 9ad7b47d8cb17873bfe38bebd866c38fbffdc034.
|
|
|
|
| |
autoreconf
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
As the Visual Studio 2012/2013 are only slightly different from the Visual
Studio 2010 projects, we can provide support for them by using scripts to
copy the Visual Studio 2010 projects, and update the specific parts as
necessary.
Thus, there would be little maintenance overhead for these as only the 2010
projects need to be kept up-to-date as a result. This might change when we
do get the stack working with WinRT/Metro, but that's going to be another
totally different issue.
|
| |
|
|
|
|
| |
For GNOME 3.13.3
|
|
|
|
|
|
| |
The g-ir-scanner has a new command line switch since commit
a882381f83f0acc6aaf7bfa03e1faa1c41a7ba00, so it'd be nice to have a
version number we can use in checks.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
There was some dependence on the serial test harness in the recent tests
that were added. Update GI to use the parallel test harness to avoid
incompatibilities.
https://bugzilla.gnome.org/show_bug.cgi?id=721477
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add Python unittest module parameterization support to gi-tester through the
use of a "TESTARGS" variable. Use the Automake test harness along with
gi-tester for running the Python annotationparser tests.
Add tests/scanner/annotationparser/Makefile.am and localize testing
rules and EXTRA_DIST setup to this file. Specific Python tests can now be
run as follows:
cd tests/scanner/annotationparser
make check TESTS=test_patterns.py TESTARGS=TestTagValueStability
https://bugzilla.gnome.org/show_bug.cgi?id=720713
|
| |
|