summaryrefslogtreecommitdiff
path: root/win32/vs10/README.txt
diff options
context:
space:
mode:
Diffstat (limited to 'win32/vs10/README.txt')
-rw-r--r--win32/vs10/README.txt15
1 files changed, 14 insertions, 1 deletions
diff --git a/win32/vs10/README.txt b/win32/vs10/README.txt
index f9fe013..80ea7bd 100644
--- a/win32/vs10/README.txt
+++ b/win32/vs10/README.txt
@@ -22,7 +22,6 @@ a compiled C program, in addition to generating the atk.pc pkg-config
file for the build. See PythonDir (32-bit builds) or PythonDirX64 (x64
builds) in atk-version-paths.props to see that they point to the correct paths.
-
a) look for all of the dependencies (except GLib*) under
http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
@@ -84,6 +83,20 @@ headers, EXEs, DLLs and LIBs will end up in
<root>\vs10\<PlatformName>\bin (EXEs/DLLs)
respectively.
+Building introspection files are now integrated in the build process of the
+solution files. In order for this to work, ensure that PythonDir (32-bit builds)
+or PythonDirX64 (x64 builds) are set at the installation directory of where your
+Python installation is. Please note the following:
+
+-This Python installation must be the same installation/configuration as the
+ one that was used to build GObject-Introspection.
+
+-g-ir-scanner needs to be found at <root>\vs10\<PlatformName>\bin, and the
+ other Python items needs to be under <root>\vs10\<PlatformName>\lib\gobject-introspection.
+
+-If this fails, the other parts of the build/"install" will still continue to proceed
+ normally, so this is optional.
+
After the build of ATK, the "install" project will copy build results
and headers into their appropriate location under <root>\vs10\<PlatformName>.
For instance, built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into