summaryrefslogtreecommitdiff
path: root/Makefile-msvcproj.am
Commit message (Collapse)AuthorAgeFilesLines
* build: Export Symbols Using Compiler DirectivesChun-wei Fan2014-08-151-1/+0
| | | | | | | | | | | Use compiler directives for exporting symbols for the build of libgirepository and also for the test libraries, like what is now done in GLib and GTK+ so that maintaining a separate .symbols (and .def files) would not be needed, in which the correct compiler directive is determined during configure time. Drop all the .def files and the .symbols file as we would not be using them anymore. https://bugzilla.gnome.org/show_bug.cgi?id=732669
* Rework The Visual Studio 2010 Build ProcessChun-wei Fan2014-01-211-2/+2
| | | | | | | | | | | | | | | | | | | 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-6/+6
| | | | | | | | | | | | | | | | | | | | | 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.
* build: prevent warnings during dist/distcheckDieter Verfaillie2013-10-091-13/+13
| | | | | | Make transforms tr '/' '\\' into tr '/' '\', leading to tr: warning: an unescaped backslash at end of string is not portable so double escape to make the warnings go away...
* MSVC Builds: Fix "Installation" Process againChun-wei Fan2013-07-191-3/+31
| | | | | | | My previous commit on this (d2613dd9) didn't quite get it right then and some items were missed from that commit. Get that corrected, and ensure also the scripts/templates in collections/ and doctemplates are "installed" accordingly.
* Visual Studio Builds: Fix "Installation" ProcessChun-wei Fan2013-06-211-2/+3
| | | | | Install the Python scripts under collections/ and doctemplates/, especially the scripts under collections are required during the run of g-ir-scanner.
* Update autotools for Visual C++ projects creationChun-wei Fan2012-10-271-0/+176
-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