summaryrefslogtreecommitdiff
path: root/build/win32/vs10/everything.vcxproj
Commit message (Collapse)AuthorAgeFilesLines
* Rework The Visual Studio 2010 Build ProcessChun-wei Fan2014-01-211-201/+0
| | | | | | | | | | | | | | | | | | | 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.
* Rework The Visual Studio 2008 Build ProcessChun-wei Fan2014-01-201-4/+4
| | | | | | | | | | | | | | | | | | | | | 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.
* Visual C++ 2010 projects: Prepare for VS 2012 supportChun-wei Fan2013-01-211-0/+4
| | | | | | | | | | | | 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.
* Add Visual Studio projectsChun-wei Fan2012-10-271-0/+197
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