| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Copy cairo-1.0.gir, which is now built during the introspection building
process.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Some functions were added or renamed in the various DLLs, so reflect these
changes there.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Be a little bit more clear on how certain environmental variables are to
be set.
|
|
|
|
|
|
| |
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?)
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
...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.
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
-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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 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
|
|
|
|
|
|
|
|
|
| |
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
|
|
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
|