summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* MSVC builds: Update NMake Makefiles for introspectionChun-wei Fan2016-01-042-6/+8
| | | | | | | | | | | This updates the NMake Makefiles for: -Removing the __pycache__ directory on clean, which is generated when using Python 3.x, in the NMake Makefiles for building the main introspection files. -Building the giteststructinfo test program, as well as moving builds of DLLs and EXEs to using inference rules when applicable, for the NMake Makefiles that is used to build the tests.
* MSVc builds: Fix last commitChun-wei Fan2016-01-042-0/+2
| | | | I missed gitestmacros.h, which will be required... :|
* MSVC builds: "Install" some of the test sourcesChun-wei Fan2016-01-042-0/+11
| | | | | Some of these test sources will be used during the test of PyGObject/PyGI, so "install" them.
* scanner: fix line number countingDieter Verfaillie2015-12-271-13/+13
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=752047
* build: dist autogen.shColin Walters2015-12-101-0/+1
| | | | | So if I patch things downstream I can more easily rebuild the autotools.
* Revert "libgirepository: Refuse to run in setuid applications"Colin Walters2015-12-092-14/+1
| | | | | | | | | | | | 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
* build/win32/gi-tests-msvc.mak: Clean up outputChun-wei Fan2015-12-021-2/+4
| | | | | | | We want to clean up the .ilk files, but only want to create them only during debug builds. Also silence some warnings during the tests by defining TOP_BUILDDIR.
* build/win32: Use PREFIX for all NMake MakefilesChun-wei Fan2015-12-023-23/+23
| | | | This makes things a bit more consistent, rather than using BASEDIR
* build/win32: Make detectenv-msvc.mak and introspection-msvc.mak genericChun-wei Fan2015-12-023-10/+27
| | | | | | | We want to have projects to share common items as much as possible, so move project-specific away from detectenv-msvc.mak and introspection-msvc.mak so that projects needing to update intropsection-msvc.mak can come back here to update it, and update detectenv-msvc.mak from $(glib_srcroot)/build/win32.
* build/win32/vs*/README.txt: Ensure line endings are consistentChun-wei Fan2015-12-022-33/+33
| | | | We need DOS/Windows line feeds here...
* girepository: Fix memory leak in g_irepository_get_dependencies()Garrett Regier2015-11-201-3/+5
| | | | | | The transitive_dependencies GHashTable was being leaked. https://bugzilla.gnome.org/show_bug.cgi?id=758448
* MSVC 2010+ builds: Fix tool scripts generationChun-wei Fan2015-11-201-2/+2
| | | | | The Python command for generating the tool scripts are mixed up for 32-bit release and 64-bit debug builds, fix that. Oops.
* build: Move MSVC-related build items to build/win32Chun-wei Fan2015-11-2021-244/+251
| | | | | | | | | | Move the NMake Makefiles modules and the Python tool scripts to build/win32, so that we may be consistent across the board. Also, update the build files and the README.txt's to make it clear to people that Python 3.3+ is now supported for building the introspection files, in addition to Python 2.7.x. Make the NMake Makefiles more flexible in powershell environments so that the variables can be properly passed in from the command line.
* gir: Update annotations from GLib git masterRico Tzschichholz2015-11-192-27/+38
|
* build/Makefile.msvc-introspection: Change PYTHON2 to PYTHONChun-wei Fan2015-11-121-1/+1
| | | | | Since the introspection scanner also supports Python 3.3+, use PYTHON instead of PYTHON2 to make this clearer to people.
* MSVC builds: Rename "install" projectChun-wei Fan2015-11-129-7/+7
| | | | | | Rename it to "gi-install" so that it will not conflict with the other projects in the GTK+ stack if used as a part of an all-in-one solution file.
* MSVC 2010+ builds: Do not explicitly use /LTCGChun-wei Fan2015-11-125-11/+0
| | | | | | | | | This partially reverts 8fbfbf3. As we now ensure that items using GResources and GConstructors are always referenced so that the linker does not optimize them out in a default Release build, we no longer need to enforce the use of /LTCG, so /LTCG:incremental will work as well.
* gir: Update annotations from GLib git masterPhilip Withnall2015-11-073-399/+731
|
* tests: Add more regression tests for (not nullable)Philip Withnall2015-11-0611-0/+345
| | | | | | | | | | | | On bug #719966, the question arose of whether parameters annotated with (element-type) but not (not nullable) are regarded as nullable or non-nullable. Add some new unit tests to Regress-1.0.gir to check the behaviour is as expected: annotating a parameter with (element-type) implicitly makes it non-nullable (unless also annotated with (nullable)). https://bugzilla.gnome.org/show_bug.cgi?id=757678
* Release 1.47.1Colin Walters2015-11-031-2/+2
|
* Update GLib annotations for 2.47.1Colin Walters2015-11-031-291/+193
|
* g-ir-tool-template: Fix a coding error that hooks up pdb in any buildMikhail Zabaluev2015-11-011-2/+2
| | | | | | | | | A condition was supposed to test if GI_SCANNER_DEBUG environment variable is unset or empty, but instead always evaluated to true. This results in any build pausing in pdb whenever an uncaught exception occurs in a g-ir-* tool. https://bugzilla.gnome.org/show_bug.cgi?id=757443
* g-ir-scanner: Set sensible permissions on the output fileMikhail Zabaluev2015-11-011-0/+8
| | | | | | | | If the file is new, set the permissions to 0644. If the file with the name specified as --output exists, copy its metadata onto the temporary output file. https://bugzilla.gnome.org/show_bug.cgi?id=757442
* Don't lose output silently when overwrite of the output file is deniedMikhail Zabaluev2015-11-011-1/+0
| | | | | | | If the move resulted in EPERM, discard the temporary output file, but raise the error so that the tool exits with a nonzero status. https://bugzilla.gnome.org/show_bug.cgi?id=757442
* giscanner/transformer.py: Fix --identifier-filter on Python 3.xChun-wei Fan2015-10-281-1/+2
| | | | | | | We need to encode the identifier-filter command to bytes, and decode its outputs to ascii in order for it to work on Python 3.x. https://bugzilla.gnome.org/show_bug.cgi?id=757126
* giscanner/dumper.py: Fix for Python 3.x for MSVC 2010+Chun-wei Fan2015-10-281-1/+2
| | | | | | | | sys.exc_clear(), which was called when we need to ignore the error when we can't embed manifests to the dumper program on MSVC 2010 and later, is only available/needed for Python 2.7.x, so only use it there. https://bugzilla.gnome.org/show_bug.cgi?id=757126
* giscanner/ccompiler.py: Make Windows builds work with Python 3.xChun-wei Fan2015-10-281-2/+2
| | | | | | | | | | Windows builds check the library that was passed into the introspection scanner to deduce the correct DLL that is to be used by the .gir/.typelib file, but this was not updated for Python 2.x/3.x compatibility, as the outputs of a subprocess must be decoded. Fix this for both MSVC and MinGW-based builds. https://bugzilla.gnome.org/show_bug.cgi?id=757126
* giscanner/msvccompiler.py: Make it compatible with Python 3.xChun-wei Fan2015-10-281-2/+2
| | | | | | This is checked for Python 2.7.x compatibility as well. https://bugzilla.gnome.org/show_bug.cgi?id=757126
* tools: Windows-re-enable 'relocatability' for tool templateChun-wei Fan2015-10-281-2/+2
| | | | | | | | The transition to Python 3.x compatibility accidentily removed the 'relocatability' support that was added, so re-enable this support on Windows again. https://bugzilla.gnome.org/show_bug.cgi?id=757126
* MSVC release builds: Ensure that /LTCG is usedChun-wei Fan2015-10-285-4/+14
| | | | | | | | | MSVC 2015 changed its default link-time code generation setting to /LTCG:incremental, which causes problems if /opt:noref is to be used, meaning that some code will be optimized out by the linker. Avoid this situtation here by enforcing the use of /LTCG for MSVC 2010+ builds.
* gir: Update annotations from GLib git masterRico Tzschichholz2015-10-252-1/+316
|
* scanner: Fix non-libtool linker flags on DarwinPhilip Chimento2015-10-201-3/+4
| | | | | | | | | Darwin's linker doesn't like "-rpath=path"; instead pass "-rpath path", which works on more linkers than the version with the = sign does. Additionally, Darwin's linker has no equivalent for "--no-as-needed" (it seems to do the right thing by default?) https://bugzilla.gnome.org/show_bug.cgi?id=625195
* tests: Usage a single allocation for test_ghash_gvalue_returnSimon Feltman2015-10-191-22/+26
| | | | | | | | Use a single static allocation for the hash created in regress_test_ghash_gvalue_return(). This function is explicitly marked as returning the hash with transfer-none and doesn't need to re-create the hash each call. https://bugzilla.gnome.org/show_bug.cgi?id=736517
* tests: Free input array in test_array_int_inout()Simon Feltman2015-10-191-0/+2
| | | | | | Transfer is annotated as full so the function should free its input. https://bugzilla.gnome.org/show_bug.cgi?id=736517
* tests: Free input string in regress_test_utf8_inout()Simon Feltman2015-10-191-0/+1
| | | | | | | Transfer is annotated as full so the function should free its input after testing and before output assignment. https://bugzilla.gnome.org/show_bug.cgi?id=736517
* tests: Unref async result after adding to idle callbackSimon Feltman2015-10-191-0/+1
| | | | | | | | g_simple_async_result_complete_in_idle() will add its own reference for managing the async result. We need to unref the result after calling this so we don't leak. https://bugzilla.gnome.org/show_bug.cgi?id=736517
* Add support for function typedefs without pointerBen Iofel2015-10-1911-2/+224
| | | | | | | | | | g-ir-scanner now supports something like this: typedef void my_callback(int); Notice how my_callback is not a pointer. https://bugzilla.gnome.org/show_bug.cgi?id=755645
* giscanner: Fix python2/3 compatibilityDamien Grassart2015-10-193-8/+8
| | | | | | | This allows building in both Python 2 and 3 by fixing a few text/binary ambiguities and using "as" in an except clause. https://bugzilla.gnome.org/show_bug.cgi?id=756763
* Generate relative paths for gio-unix C header includesMikhail Zabaluev2015-10-191-2/+4
| | | | | | | | | In the generated GIR for Gio-2.0, the <c:include/> elements for gio-unix headers got emitted with absolute pathnames. Obviously, this does not work well when GIR needs to be checked into repositories, is used to build in other locations, etc. https://bugzilla.gnome.org/show_bug.cgi?id=756679
* Salvage the build directory parameter of update-glib-annotations.pyMikhail Zabaluev2015-10-151-9/+8
| | | | | | | It was not possible to use the tool with a custom build directory, even when it was given as the second command line parameter. https://bugzilla.gnome.org/show_bug.cgi?id=756665
* gir: Update annotations from GLib git masterColin Walters2015-10-123-52/+162
|
* repository: Fix format string error in previous commitColin Walters2015-10-121-1/+1
| | | | Regression from df21d1f362a810f48a23b7c121bf09ce398539c7
* transformer: Strip out GLib _autoptr typedefsColin Walters2015-10-101-0/+3
| | | | | | | They're just internal bits for users of C, shouldn't be part of the API. https://bugzilla.gnome.org/show_bug.cgi?id=755882
* girepository: Use constant time calculation for sections after Object fieldsSimon Feltman2015-10-106-53/+101
| | | | | | | | | | | | Add "n_field_callbacks" to ObjectBlob which represents the number of object fields which are also callbacks. This a allows a constant time computation for accessing sections after fields. Track writing of this field by passing an extra argument through the girnode writers recursive call structure. This essentally reverts a portion of commit 7027bb256d0d1ab which added a linear time computation for accessing sections after fields. Update typelib validator to also ensure n_field_callbacks is properly set. https://bugzilla.gnome.org/show_bug.cgi?id=700338
* maintransformer: Fix regression in callback closure assignmentColin Walters2015-10-103-32/+20
| | | | | | | The nullable code needs to search via index lookup of closure_name, which drops the need to (incorrectly) assign closure_name again. https://bugzilla.gnome.org/show_bug.cgi?id=756352
* giscanner.message: Don't print node as the default contextMikhail Zabaluev2015-10-051-3/+1
| | | | | | | Node is always present in the output of .log_node(), so printing it another time as context just adds noise. https://bugzilla.gnome.org/show_bug.cgi?id=756088
* build: Add test XML file to buildPhilip Withnall2015-10-051-0/+1
| | | | | | | Fixup to commit 10cb665fee2cc378dd2f13bad16e6384836a8b16. I failed to work git properly when submitting the patch. https://bugzilla.gnome.org/show_bug.cgi?id=729660
* build: Add an autotools module for introspection builds on MSVCChun-wei Fan2015-10-052-2/+128
| | | | | | | | | | | | This adds an autotools module that can be included in projects to be used for generating the command lines for g-ir-scanner and g-ir-compiler for introspection builds on Visual Studio builds. This is currently not used directly in the MSVC builds of g-i, but is added here as other modules are directly to get this file from here (i.e. $(srcroot)/build) for inclusion in their Makefile.am's to support introspection builds for modules that support Visual Studio builds.
* giscanner: Mark gpointer nodes as nullable by defaultPhilip Withnall2015-10-049-29/+184
| | | | | | | | | | | | | gpointer parameters and return types should be marked as nullable by default, unless: • also annotated with (type) and not with (nullable); or • explicitly annotated with (not nullable). This introduces the (not nullable) annotation as a direct opposite to (nullable). In future, (not) could be extended to invert other annotations. https://bugzilla.gnome.org/show_bug.cgi?id=729660
* giscanner: Mark (closure) parameters as (nullable) by conventionPhilip Withnall2015-10-043-20/+107
| | | | | | | | All user_data pointers should be nullable, and they should all be annotated as closures too. I have not found any counter-examples where a closure is non-nullable. https://bugzilla.gnome.org/show_bug.cgi?id=729660
View Lorry Controller Status