summaryrefslogtreecommitdiff
path: root/build
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Build: Provide Simple Support for MSVC 2012/2013Chun-wei Fan2014-07-014-1/+146
| | | | | | | | | | | | 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.
* 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/gi-introspection-msvc.mak: Fix Build and InstallationChun-wei Fan2014-04-161-1/+3
| | | | | | | | Copy the .gir files that are bundled with g-i to build/ before trying to compile the .gir's that were generated during the build process, so that the compilation of these .gir's may succeed. Also, create the share/gir-1.0 and lib/girepository-1.0 directories, if needed, before trying to copy the .gir/.typelib files.
* build/gi-introspection-msvc.mak: Fix Include PathChun-wei Fan2014-04-011-2/+2
| | | | | | The -I flags for generating GIRepository-2.0.gir should use $(BASEDIR), not %BASEDIR%, as we are not using a Windows .bat to generate the introspection files.
* MSVC Builds: Update Introspection Build ProcessChun-wei Fan2014-02-251-10/+5
| | | | | | | | The introspection build on Windows recently received support to deduce the DLL name from the library that is passed into g-ir-scanner, so the library name (without the file name extensions, etc) ought to be passed in for the build of introspection files on Windows, just like the *nix builds of g-i.
* Visual Studio 2008 Build: Further RefinementsChun-wei Fan2014-01-212-3/+3
| | | | | Fix up more grammar stuff in the README.txt file, and fix the CLEANFILES line.
* Rework The Visual Studio 2010 Build ProcessChun-wei Fan2014-01-2134-1038/+555
| | | | | | | | | | | | | | | | | | | This patch makes the build of G-I on Visual Studio 2010 into a two-step process, as it would make it clearer and easier to the one building G-I by: -Splitting up the property sheets into multiple parts, where pre-configured code (which is currently shipped with the tarball) is copied using custom build steps, so that they can be re-copied when they are updated. This also removes the need for setting environment variables before launching the Visual Studio Project to build the G-I DLL, the tools written in C and the _giscanner Python2 module. The Python2 paths (set to Python 2.7.x) are now set in a property sheet, which can be updated quite easily, if needed. -Directing people to use the set of NMake Makefiles to build the introspection files for GLib, and also the .gir's that are shipped with G-I, which was added in a previous commit, as it would make it clearer what are needed to build the introspection files.
* build/gi-introspection-msvc.mak: Correct a Library NameChun-wei Fan2014-01-211-1/+1
| | | | | | Otherwise the .gir/.typelib for the GIRepository DLL would not be build correctly-leftover oops when reworking the introspection files build process.
* build/win32/vs9: Minor UpdatesChun-wei Fan2014-01-214-4/+4
| | | | | | Fix grammar and formatting of items, remove a line in the README.txt that is currently not true, and avoid including an extra property sheet that isn't really needed.
* build/win32/vs9/Readme.txt: Remove Extra Blank LineChun-wei Fan2014-01-211-1/+0
|
* Rework The Visual Studio 2008 Build ProcessChun-wei Fan2014-01-2046-888/+1094
| | | | | | | | | | | | | | | | | | | | | This patch makes the build of G-I on Visual Studio 2008 into a two-step process, as it would make it clearer and easier to the one building G-I by: -Splitting up the property sheets into multiple parts, where pre-configured code (which is currently shipped with the tarball) is copied using custom build steps, so that they can be re-copied when they are updated. This also removes the need for setting environment variables before launching the Visual Studio Project to build the G-I DLL, the tools written in C and the _giscanner Python2 module. The Python2 paths (set to Python 2.7.x) are now set in a property sheet, which can be updated quite easily, if needed. -Use a set of NMake Makefiles to build the introspection files for GLib, and also the .gir's that are shipped with G-I, and make it clear to people what things are needed to build the introspection files. -Standardizing across the board that we now use $(ApiVersion) for the .lib files and the "installation" of headers, etc. Similar updates to the Visual Studio 2010 files will follow later.
* gimarshallingtests.def: Add symbols for new testsChun-wei Fan2013-10-071-1/+6
| | | | | | | Add the new symbols to export for the new tests introduced in commits a19bfeb4 (gimarshalingtests: Add tests for multiple utf8 args with allow-none) and 6c9e4d5d (gimarshalingtests: Add tests for mixed allow-none and implicit args).
* Update gengir.batChun-wei Fan2013-09-181-1/+1
| | | | | Commit 08958a30 added a gmodule-2.0.c that is to be used to generate the .gir file for GModule. Update gengir.bat accordingly for GModule-2.0.gir.
* build/win32/gengir.bat: Process win32-1.0.girChun-wei Fan2013-08-061-6/+8
| | | | | | ...and include it when we generate GLib-2.0.gir as the Windows types are used from there on, and update the .typelib compilation command lines accordingly, as it will be referenced.
* Visual Studio builds: Update _giscanner ProjectChun-wei Fan2013-07-192-8/+8
| | | | | | Add the "PC" folder in the Python installation root as one of the include folders, as that is where pyconfig.h would reside (at least for the people that compiled Python themselves from source using Visual Studio)
* Update gengir.bat for Visual Studio buildsChun-wei Fan2013-03-201-0/+1
| | | | | Copy cairo-1.0.gir, which is now built during the introspection building process.
* Visual Studio builds: Process cairo-1.0.gir.inChun-wei Fan2013-03-123-0/+75
| | | | | | | | | | | | Use a simple Python script that uses Python REGEX abilities to create cairo-1.0.gir from cairo-1.0.gir.in with the correct values for Cairo, for use in the Visual Studio builds of g-i. It can be later extended if needed. Also dist this, and call this script from gengir.bat so that cairo-1.0.gir and cairo-1.0.typelib can be built and "installed" https://bugzilla.gnome.org/show_bug.cgi?id=692165
* Update def files for various test DLLsChun-wei Fan2013-02-225-100/+149
| | | | | Some functions were added or renamed in the various DLLs, so reflect these changes there.
* Visual C++ builds: "Install" gdump.cChun-wei Fan2013-01-222-0/+7
| | | | | The gdump.c source/data file was missed from the "install" process, which is required for a proper installation of G-I. Make up for that.
* build/win32/gengir.bat: Process the bundled .gir filesChun-wei Fan2013-01-211-0/+12
| | | | | | | | This will compile the .typelib files for FreeType, GL and libxml2, and copy the these .gir and their resulting .typelib files to the appropriate folder to prepare for the "install" phase. Note that the ones that aren't normally used in Windows are not processed.
* Update Visual C++ README.txt files.Chun-wei Fan2013-01-212-4/+8
| | | | | Be a little bit more clear on how certain environmental variables are to be set.
* Fix _giscanner Python module Visual C++ projectsChun-wei Fan2013-01-212-0/+8
| | | | | | We need to force-include io.h as there is no longer a prototype for isatty() in the generated scannerlexer.c source file, which broke the build. (possibly due to a flex program or calling change/update?)
* Visual C++ 2010 projects: Prepare for VS 2012 supportChun-wei Fan2013-01-2119-0/+76
| | | | | | | | | | | | Add the PlatformToolset tag to the project configs so that we can use a simple script later to the autotools files to copy the projects and change the value of that tag (v100 -> v110, and other simple changes) in order that we can quickly provide and maintain support for Visual Studio 2012 with minimal effort. Note that at the moment G-I does not yet support the API/SDK requirements for Windows 8 Modern UI (formerly known as Metro), but this paves the very initial step.
* Visual C++ projects: Update .sln/README.txt line endingsChun-wei Fan2013-01-214-617/+617
| | | | | | | | ...So that they will have Windows line endings. Specifically, this is something that affects how Windows detect the Visual Studio version from the .sln files, and the README.txt's should have Windows line endings.
* Add a Windows .bat to generate typelibsChun-wei Fan2012-10-271-0/+267
| | | | | | | | | | This will enable one to generate the .gir and .typelib files for GLib, GModule, GObject, GIO and G-I without using a bash-style shell on Windows. This is also the .bat that is used during the Visual C++ build process to generate the .gir and .typelib files https://bugzilla.gnome.org/show_bug.cgi?id=681820
* Update autotools for Visual C++ projects creationChun-wei Fan2012-10-274-0/+93
| | | | | | | | | -Add Makefile-msvcproj.am to fill in the cmph, girepository and g-ir-compiler projects -Add various Makefile.am's under build/ to distribute the Visual C++-related files. https://bugzilla.gnome.org/show_bug.cgi?id=681820
* Add Visual Studio 2008/2010 Solution filesChun-wei Fan2012-10-272-0/+445
| | | | | | | | These are the master solution files that will load the Visual C++ projects for building/generating gobject-introspection and its related tools and files. https://bugzilla.gnome.org/show_bug.cgi?id=681820
* Add Visual Studio projectsChun-wei Fan2012-10-2757-0/+7218
| | | | | | | | | | | | | | | | | | | | | | These are the Visual C++ 2008/2010 project files that can be used to build gobject-introspection. The main girepository dll (along with cmph), tools (in C), certain test/sample programs dlls are built with this project file set. Due to a bug in the Visual C++ 2008 linker, the g-ir-compiler and g-ir-generator tools have the libgirepository-internals sources built along side with the sources of these respective tool programs. In order to ease future maintenance, the cmph, girepository, g-ir-compiler and property sheets (for the "install" part) are done as templates where header/source listings are filled in during "make dist", so that the headers/sources listings are kept up to date between releases. The GLib and girepository .gir and .typelib files are also generated and "compiled" as part of the build process, using gengir.bat that was committed earlier. https://bugzilla.gnome.org/show_bug.cgi?id=681820
* Add README.txt files for Visual C++ buildsChun-wei Fan2012-10-272-0/+172
| | | | | | | | Add instructions to tell people how to build gobject-introspection with Visual C++, especially as there are special steps and additional requirements for a successful build. https://bugzilla.gnome.org/show_bug.cgi?id=681820
* Add a test_gir_cmd.txt fileChun-wei Fan2012-10-271-0/+117
| | | | | | | | | This is to show how one may be able to generate the .gir files from the various DLL files in tests\ in a standard Windows cmd.exe prompt, which will also attempt to demonstrate how .gir files are generated without a shell. https://bugzilla.gnome.org/show_bug.cgi?id=681820
* Add .def files for building the various DLLs (.la's) in test\Chun-wei Fan2012-10-2710-0/+1030
This will enable the exports of functions to create the .lib files needed to create the .gir files. https://bugzilla.gnome.org/show_bug.cgi?id=681820
View Lorry Controller Status