mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-18 17:30:10 +00:00
931faeab12
Since GDK-Pixbuf is now in a package of its own, stop the distribution of GDK-Pixbuf projects (those files are no longer referenced in the GTK+ solution file already) |
||
|---|---|---|
| .. | ||
| gdk-pixbuf-csource.vcproj | ||
| gdk-pixbuf-query-loaders.vcproj | ||
| gdk-pixbuf.vcproj | ||
| gdk-win32.vcproj | ||
| gdk.vcprojin | ||
| gtk-demo.vcproj | ||
| gtk.vcprojin | ||
| gtk+.sln | ||
| gtk+.vsprops | ||
| install.vcproj | ||
| Makefile.am | ||
| README.txt | ||
Note that all this is rather experimental. This VS9 solution and the projects it includes are intented to be used in a GTK+ source tree unpacked from a tarball. In a git checkout you first need to use some Unix-like environment or manual work to expand the files needed, like config.h.win32.in into config.h.win32 and the .vcprojin files here into corresponding actual .vcproj files. You will need the parts from below in the GTK+ stack: pango, atk and glib. External dependencies are at least zlib, libpng, proxy-libintl, fontconfig, freetype, expat. See the corresponding README.txt file in glib for details where to unpack them. The "install" project will copy build results and headers into their appropriate location under <root>\vs9\<PlatformName>. For instance, built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into <root>\vs9\<PlatformName>\lib and GTK+ headers into <root>\vs9\<PlatformName>\include\gtk-2.0. This is then from where project files higher in the stack are supposed to look for them, not from a specific GLib source tree. --Tor Lillqvist <tml@iki.fi>