| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
This is to test GJS's support of GValues boxed inside GValues.
https://bugzilla.gnome.org/show_bug.cgi?id=688128
|
|
|
|
|
|
|
| |
These will be used by pygobject in
https://bugzilla.gnome.org/show_bug.cgi?id=726484
https://bugzilla.gnome.org/show_bug.cgi?id=780652
|
|
|
|
|
|
|
| |
This patch fixes an issue in dumper.py, which causes a wrong oder of -L options to be passed to libtool. This
in turn can cause build failures if old library files are present in the linked library directories.
https://bugzilla.gnome.org/show_bug.cgi?id=778507
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
str.split() does not handle quoting, so if you have spaces in your
CFLAGS, it will be split incorrectly. For instance:
CFLAGS="'-I/opt/some dir' -DFOO=bar"
>>> os.environ['CFLAGS'].split()
["'-I/opt/some", "dir'", '-DFOO=bar']
>>> shlex.split(os.environ['CFLAGS'])
['-I/opt/some dir', '-DFOO=bar']
https://bugzilla.gnome.org/show_bug.cgi?id=778971
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We now reuse _create_type_from_base instead of reimplementing
it in a semi-broken way in transformer, and use complete_ctype
when writing it out if available.
This incidentally allows us to remove a test where the comment
acknowledged the non-optimal behaviour.
https://bugzilla.gnome.org/show_bug.cgi?id=779959
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We can't just use -llibxml2 for the libraries that libxml2 will link to,
as that will result in xml2.lib being searched rather than libxml2.lib
that we need, as the --msvc-syntax flag will eliminate the lib prefix for
the libraries. Instead, just pass in libxml2.lib explicitly to work around
this.
|
|
|
|
|
|
|
|
|
| |
This makes sure that all the test sources that the autotools builds
install are "installed" by the Visual Studio builds as well.
For doing this, move the generation of everything.[c|h] to
gi-introspection-msvc.mak as we need to generate them for all builds, not
just during building the tests.
|
|
|
|
|
|
| |
This module is not used in G-I itself, but is copied and used in other
modules, so make sure paths in here are up-to-date after the project moved
to win32/ from build/win32
|
|
|
|
|
|
|
| |
This is a follow-up commit to Evan Nemerson's addition to Makefile.introspection
so that we can pass in a number of C includes so that we make generate the
full NMake Makefile module with the command line to call g-ir-scanner in a
simpler and cleaner way.
|
|
|
|
|
|
| |
Sync this file from GLib so that we can support Visual Studio 2017,
which is needed for the NMake Makefiles that are used to build the
introspection to work (which, are called from the project files).
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=678749
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... 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.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=778509
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=760056
|
|
|
|
|
|
|
| |
We could have a fundamental type A derived by a subclass B. Class A happens
to be introspected, but B isn't. This can cause some issues in Gjs.
https://bugzilla.gnome.org/show_bug.cgi?id=760056
|
|
|
|
|
|
| |
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/.
|
|
|
|
|
|
|
|
| |
The Makefile.msvcproj and Makefile-newvs.am has been updated to accomodate
visual Studio 2013 as the baseline Visual Studio version that we will
support, so we need to update some things as well.
We will later move the Visual Studio projects from build/win32/ to win32/
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the only way to get a library to link against the dumper
program is through '--link' which implies that library will be defined
in the 'libraries' field of the .gir. When using libtool, we
link against dependencies of that library as the .la defines that, but
when using --no-libtool that won't happen and the user needs to be
able to define to what other libraries the program needs to be link
against, and this is what the new --extra-library argument is about.
https://bugzilla.gnome.org/show_bug.cgi?id=774625
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since autoptr typedefs are filtered out (bug #755882), scanning this header
is useless. It can cause warnings due to not #including all the headers
whose types it references:
/usr/include/glib-2.0/glib/glib-autocleanups.h:41: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef
GAsyncQueue *GAsyncQueue_autoptr;' at 'GAsyncQueue_autoptr'
Fix that by filtering it out of the list of headers to scan.
https://bugzilla.gnome.org/show_bug.cgi?id=768816
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Visual Studio 2015 does not like collection of paths that exceed 260
characters, and we have a good number of items that we want to track in
the NMake Makefiles for building introspection, and the projects demand
full paths for NMake outputs for projects using NMake. Work around this
by listing only the most key files that are built, since the NMake
Makefile rules will take care of the rest.
|
|
|
|
|
|
|
| |
We previously moved the NMake Makefiles to build the introspection files
into build/win32, but I forgot to change the LIB envvar setting to reflect
that, causing introspection builds to fail for GIRepository-2.0.gir (or to
use a previously-installed version of girepository-1.0.lib). Fix this.
|
|
|
|
| |
The "install" project didn't copy the .lib file. Fix that.
|
| |
|
|
|
|
|
|
|
| |
In order to test GJS's support for GHashTables with float, double,
gint64, and guint64 value types, here are some new GI marshalling tests.
https://bugzilla.gnome.org/show_bug.cgi?id=773763
|
|
|
|
|
|
| |
Like the autotools builds, include this file as well when we generate
Gio-2.0.gir. This is a follow-up commit for b8d92b0 (Gio-2.0.gir:
Don't exclude gsettingsbackend.h and pass needed define).
|
|
|
|
|
| |
The wrong source file was listed in the projects, and the tool ought to be
"installed". Sorry!
|
| |
|
| |
|
|
|
|
|
| |
Sorry, this is a bit late to the party, but we should build this tool for
Visual Studio builds as well.
|
|
|
|
|
| |
This is to ensure that the chamges that is applied to gi-install.props here is
applied to the project files in build/win32/vs[11|12|14] as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the Makefile*.am targets for generating the Visual Studio projects
re-generate the project files and the header listings wheneer the
Makefile*.am's that include build/Makefile.msvcproj changes, so that
whenever a source/header is added or removed, they will be reflected
in the prohects and in the property sheets that are used to copy the
headers.
Also ensure that these are applied to the vs11, vs12 and vs14 projects
this happens, as they are copied and processed from the Visual Studio
2010 projects.
|
|
|
|
|
|
| |
Left over from code review fix.
https://bugzilla.gnome.org/show_bug.cgi?id=772790
|
|
|
|
|
|
|
|
| |
For boolean arrays, we want to make sure that we actually got an array of
TRUE and FALSE (1 and 0) instead of an array of integers that may have
other values besides 1 and 0.
https://bugzilla.gnome.org/show_bug.cgi?id=772790
|
|
|
|
|
|
|
| |
Since we return a static const array as the out value, the function must
have a const type for its out parameter.
https://bugzilla.gnome.org/show_bug.cgi?id=772790
|