summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* girepository: Add Header for Version MacrosChun-wei Fan2014-08-1523-0/+506
| | | | | | | | | | | | | | | This adds a header to the girepository library, which is then included either directly or indirectly by the other headers so that all the public symbols (and the 2 symbols in gitypelib-internal.h used by the tools) are decorated by a macro, that can later be used to export the symbols and also to be used to display compile-time warnings for usage of deprecated APIs, which is like what is now being done in GLib (and GTK+, Clutter, and so on). This marks the first step that we begin to stop depending on the .symbols/ .def files to export the symbols. https://bugzilla.gnome.org/show_bug.cgi?id=732669
* tests: Add a Header for Symbol ExportingChun-wei Fan2014-08-152-2/+14
| | | | | | | | | | 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
* tests/repository: Drop Unneeded IncludesChun-wei Fan2014-08-133-3/+0
| | | | | | | 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 Regress-1.0-sections-expected.txtSimon Feltman2014-08-071-0/+1
| | | | | | Update based additional test added with commit e2b96aaa4 https://bugzilla.gnome.org/show_bug.cgi?id=702508
* tests: Add regression test for callbacks with an inout arrayGarrett Regier2014-08-079-0/+283
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=702508
* tests: Add constructor with an error argumentGarrett Regier2014-08-072-0/+14
| | | | | | Make sure a constructor that sets a GError works correctly. https://bugzilla.gnome.org/show_bug.cgi?id=727004
* Check for MINGW instead of MINGW32Ignacio Casal Quinteiro2014-08-061-1/+2
| | | | | | New versions of msys2 provide a MINGW64 env variable instead. https://bugzilla.gnome.org/show_bug.cgi?id=734163
* giscanner: Add New CCompiler ModuleChun-wei Fan2014-08-054-157/+222
| | | | | | | | | | | | | | | This adds a CCompiler module for the giscanner Python scripts so that items related to the run of the preprocessor, compiler and linker can be done in this module, and this marks the beginning of the move of building the introspection files using Python's distutils. This patch first moves _add_[internal|external]_link_flags() to ccompiler.py as get_[internal|external]_link_flags and also moves the Windows shlibs resolution (deducing the DLLs the introspection files should link to from the libraries passed in) in shlibs.py to resolve_windows_libs() in ccompiler.py https://bugzilla.gnome.org/show_bug.cgi?id=728313
* giscanner/cachestore.py: Clean up a bitChun-wei Fan2014-08-011-4/+1
| | | | | | | Use the special os.path.expanduser('~'), as it it more portable, instead of quering the HOME or HOMEPATH envvar. https://bugzilla.gnome.org/show_bug.cgi?id=732668
* doap category coreOlav Vitters2014-07-301-0/+1
|
* Post-release version bump to 1.41.5Giovanni Campagna2014-07-221-1/+1
|
* Release 1.41.4GOBJECT_INTROSPECTION_1_41_4Giovanni Campagna2014-07-221-2/+2
| | | | And update glib annotations from glib 2.41.2
* Update glib annotations from masterFlorian Müllner2014-07-103-5/+71
|
* girepository: Include config.h First in All SourcesChun-wei Fan2014-07-0720-6/+40
| | | | | | | | | This includes config.h in all the C-sources of girepository so that we can get the correct export directive from config.h during compile time and therefore export the symbols as necessary, like what GLib and GTK+ is currently doing. https://bugzilla.gnome.org/show_bug.cgi?id=732669
* giscanner: Make _get_cachedir() Always Work on WindowsChun-wei Fan2014-07-041-1/+4
| | | | | | | | | | On Windows, checking for $(HOME) will work in a MSYS shell but not in cmd.exe (i.e. Visual Studio command prompt), so we need to check for HOMEPATH when we are building under a Visual Studio command prompt to get the users's home directory correctly. This will enable g-ir-doc-tool to work on Windows when run from cmd.exe. https://bugzilla.gnome.org/show_bug.cgi?id=732668
* MSVC Builds: Drop Test DLL ProjectsChun-wei Fan2014-07-0431-3464/+0
| | | | | | | This drops Visual Studio projects that does the build of the Test DLLs, as the new NMake Makefiles will cover the building of them. Please note that the cmph test program is still built with the Visual Studio projects though.
* Visual Studio Projects: Don't Build the Test DLLsChun-wei Fan2014-07-042-207/+0
| | | | | | | The NMake Makefiles that build the tests cover these, so remove the parts building the Test DLLs from the solution files. This is done as a separate commit as solution files must have DOS/Windows line endings, not UNIX line endings.
* MSVC Builds: Add NMake Makefiles to Build the TestsChun-wei Fan2014-07-047-145/+328
| | | | | | | | | | | | This adds NMake Makefiles for one to build the tests for Visual Studio builds, which is not done with an MSYS shell. Shared items from the existing NMake Makefiles for building the introspection files, which are also used to build the tests, are split out into common NMake Makefiles, which are then included. This also means that we do not need to include the test_gir_cmd.txt for people to look at when building the tests as the NMake Makefiles will do the job for them, which cover the material there.
* MSVC Builds: "Install" glib-print demoChun-wei Fan2014-07-042-0/+4
| | | | | ...so that people can use it as a first check that g-i and the introspection files are built properly.
* MSVC 2010 Projects: Improve Optimization A BitChun-wei Fan2014-07-041-2/+1
| | | | | | | | As the MSVC 2010 x64 (and later) compiler/linker do not have the optimization bug that prevents g-ir-compiler.exe from being built (due to a compiler/linker hang) under /O2 (max speed) (or /Ox, complete optimization), use /O2 for the optimization setting, like the other parts of g-i under Visual Studio 2010.
* detectenv_msvc.mak: Add MSVC 2008 x64-specific CFLAGChun-wei Fan2014-07-041-0/+4
| | | | | | | | Due to an optimization bug in the Visual Studio 2008 x64 compiler/linker, compilation of some programs shipped with g-i will hang, so use different optimization settings for it, so that programs built through the NMake Makefiles can build correctly. A similar setting for the g-ir-compiler is already in there.
* Parse and expose ownership transfer for instance parametersGiovanni Campagna2014-07-0315-6/+262
| | | | | | | | | | | 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
* Update glib annotations from git masterRico Tzschichholz2014-07-023-16/+51
|
* Windows port: Make g-ir-annotiotion-tool, g-ir-doc-tool and g-ir-scanner ↵Dieter Verfaillie2014-07-023-7/+34
| | | | | | 'relocatable' at runtime. https://bugzilla.gnome.org/show_bug.cgi?id=620566
* Build: Provide Simple Support for MSVC 2012/2013Chun-wei Fan2014-07-015-2/+149
| | | | | | | | | | | | 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.
* Update Visual Studio Property SheetsChun-wei Fan2014-07-012-6/+6
| | | | | Standardize on using VSVer, like the other parts of the GTK+/Clutter stack, it makes it easier to use a script to support later Visual Studio versions.
* MSVC Builds: Clean Up .gir GenerationChun-wei Fan2014-07-011-9/+1
| | | | | | | | Since commit f3128da2 we are passing in the .lib('s) to deduce the DLL(s) that the introspection files need to look, so we don't have to make an extra copy of the .lib that matches the <namespace-name>-<namespace-version> convention anymore. Clean up a bit as a result.
* Post-release version bump to 1.41.4Giovanni Campagna2014-06-251-1/+1
|
* Release 1.41.3GOBJECT_INTROSPECTION_1_41_3Giovanni Campagna2014-06-251-1/+1
| | | | For GNOME 3.13.3
* Update glib annotations from glib 2.41.1Giovanni Campagna2014-06-253-31/+140
|
* gibaseinfo: Expand g_base_info_iterate_attributes() documentationPhilip Withnall2014-06-231-1/+4
| | | | | | | Clarify what an attribute is, in response to a question on gir-devel-list. https://bugzilla.gnome.org/show_bug.cgi?id=732078
* Bump g-i versionEmmanuele Bassi2014-06-201-1/+1
| | | | | | 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.
* Fix on Last CommitChun-wei Fan2014-06-091-4/+4
| | | | | There aren't architecture-specific naming for binaries for g-i on Windows, so don't bother checking for them.
* MSVC 2010+ Projects: Update "Installation" ProcessChun-wei Fan2014-06-092-17/+33
| | | | | | | | | | | | | | | Currently, due to the way that Visual Studio 2010+ projects are handled, the "install" project does not re-build upon changes to the sources, as it does not believe that its dependencies have changed, although the changed sources are automatically recompiled. This means that if a part or more of the solution does not build, or if the sources need some other fixes or enhancements, the up-to-date build is not copied automatically, which can be misleading. Improve on the situation by forcing the "install" project to trigger its rebuild, so that the updated binaries can be copied. This does trigger an MSBuild warning, but having that warning is way better than not having an up-to-date build, especially during testing and development.
* build: Fix distcheck after addition of identifier filteringSimon Feltman2014-06-031-1/+2
| | | | | Add missing identfilter.py to EXTRA_DIST and correct spelling of Identfilter-1.0-expected.gir.
* scanner: Add --identifier-filter-cmdSimon Feltman2014-06-037-3/+173
| | | | | | | | | 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
* gimarshallingtests: Correctly retrieve param spec's value typeMatijs van Zuijlen2014-05-301-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=728409
* Update glib annotations from git masterRico Tzschichholz2014-05-241-71/+78
|
* Update glib annotations from git masterRico Tzschichholz2014-05-243-42/+63
|
* girepository: change giarginfo docsRyan Lortie2014-05-141-3/+8
| | | | | | | Clarify the meaning of 'may be null' in the docs: it refers to the value of the argument itself, not the reference to the argument. https://bugzilla.gnome.org/show_bug.cgi?id=660879
* annotationparser: more nullable fixesRyan Lortie2014-05-081-0/+2
| | | | | Add ANN_NULLABLE and ANN_OPTIONAL in the one (and only) other place that ANN_ALLOW_NONE is mentioned...
* tests: fix Regress expected outputRyan Lortie2014-05-071-2/+11
| | | | | Now that Cancellable and AsyncReadyCallback are being correctly recognised again, adjust the expected output of the Regress testcase.
* giscanner: allow (nullable) and (optional)Ryan Lortie2014-05-071-2/+2
| | | | | | | Add (nullable) and (optional) as recognised annotations in the same places that (allow-none) is allowed. This should have been done in the previous commits but the tests were passing because the only ill effect was that a warning was issued.
* Revert "giscanner: don't accept (allow-none) on Returns:"Ryan Lortie2014-05-066-39/+36
| | | | | | | 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.
* giscanner: fix a comparisonRyan Lortie2014-05-061-1/+1
| | | | | | | | In the case that a parameter has not been explicitly annotated, the value of node.direction will be None, not 'in'. Instead of comparing as == 'in' we should therefore check for being != 'out'. https://bugzilla.gnome.org/show_bug.cgi?id=660879
* compiler: girparser: parse 'nullable' attributeRyan Lortie2014-05-061-1/+16
| | | | | | | | | | | Parse the 'nullable' attribute on parameters and function return types. Additionally, tweak the meaning of the 'allow-none' attribute. We now only treat it as equivalent to 'nullable' for non-out parameters. For out parameters, we treat it to mean the same as the already-recognised 'optional' parameter (which we only recently started actually using). https://bugzilla.gnome.org/show_bug.cgi?id=660879
* girepository: ArgBlob: rename allow_none parameterRyan Lortie2014-05-065-11/+11
| | | | | | | | | Rename the "allow_none" parameter on internal/private structure ArgBlob to "nullable". This is a straight rename with no other changes. https://bugzilla.gnome.org/show_bug.cgi?id=660879
* giscanner: support nullable return types tooRyan Lortie2014-05-063-6/+9
| | | | | | | | | | Promote the 'nullable' field to the TypeContainer base class (which is shared by Return and Parameter types). Add .gir support for nullability on return values, both in the writer and in the (scanner's) parser. https://bugzilla.gnome.org/show_bug.cgi?id=660879
* giscanner: add (nullable) and (optional) annotationsRyan Lortie2014-05-062-1/+33
| | | | | | | | | | | Add two new annotations, (nullable) and (optional). (nullable) always means "the type of this value can also contain null". (optional) always means "this out parameter can be ignored by passing NULL to the C function". https://bugzilla.gnome.org/show_bug.cgi?id=660879
* giscanner: write nullable and optional attributesRyan Lortie2014-05-064-21/+70
| | | | | | | | | | | | | | | | | | | 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
View Lorry Controller Status