| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The wrong source file was listed in the projects, and the tool ought to be
"installed". Sorry!
|
| |
|
|
| |
This is needed so that gtk+-3.0.pc will be complete.
|
| |
|
|
|
|
|
|
|
| |
That is, for Cairo, Freetype and libxml2, as packages that we support
for Visual Studio builds depend on these packages, specifically for
generating the introspection files for them.
These are generated with rather generic info in them, so that they are
sufficient for our purposes here.
|
| |
|
|
|
|
|
| |
Generate the .pc files as part of the build of the Visual Studio projects,
and "install" them to $(CopyDir)\lib\pkgconfig, so that it would make it
easier for packages building introspection to find the .pc files for g-i
for Visual Studio builds.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GLib has been recently updated to optionally generate the .pc files
within the MSVC builds, which is needed to build the introspection
files, if Python is available. As we are looking for the .pc files from a
common location as a result, we can build the introspection files within
the project files, so that the build process does not have to be split
into 2 stages.
This is done by using wrapper projects that calls the NMake Makefiles that
is used to build the introspection files.
Note that although the IDE claims that the introspection
files failed to build, but they are really generated-so some investigation
is needed to see whether we can silence those false-positive errors.
Also clean up the property sheets a bit.
|
| |
|
|
| |
I missed gitestmacros.h, which will be required... :|
|
| |
|
|
|
| |
Some of these test sources will be used during the test of PyGObject/PyGI,
so "install" them.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
This makes use of the common autotools modules that was just added so that
there would need to be less items in g-i's main Makefile-msvcproj.am, so that
we can generate the complete Visual Studio 2008/2010 project files (which
will then be used to obtain the Visual Studio 2012 and 2013 projects) and
the property sheets to "install" the built binaries and headers.
|
| |
|
|
|
|
| |
Copy the .pdb files with the built DLLs and EXEs, so that it would make it
easier fore people that are developing G-I for are developing items using
G-I, since we are already generating the .pdb files for all builds.
|
| |
|
|
|
| |
...so that people can use it as a first check that g-i and the
introspection files are built properly.
|
|
|
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.
|
