1. 06 Mar, 2011 1 commit
  2. 05 Mar, 2011 5 commits
  3. 02 Mar, 2011 3 commits
  4. 01 Mar, 2011 1 commit
  5. 24 Feb, 2011 1 commit
  6. 23 Feb, 2011 4 commits
    • Chun-wei Fan's avatar
      Remove uneeded items from VS10 folder · 24d6831e
      Chun-wei Fan authored
      There is no install.vcxproj.filters...oops
      24d6831e
    • Chun-wei Fan's avatar
      Visual C++ 2010 Project Files · c8a0febc
      Chun-wei Fan authored
      These are the VS 2010 project files themselves.  Like the VS9 files, the
      main gdk-pixbuf project (*.vcxproj, *.vcxproj.filters) are expanded from
      templates during "make dist" as there may be addition of source files for
      the main library from time to time.  This is done in order to simplify
      maintenance (please see my last commit)
      
      This will build the main gdk-pixbuf library (with image loaders built in),
      and will also build the gdk-pixbuf-csource and gdk-pixbuf-query-loaders
      utility programs.  Like the VS9 project files, one can choose to use GDI+
      or the Non-GDI+ (libtiff, libjasper, IJG JPEG etc.) configurations for
      building the main gdk-pixbuf library.
      
      Comments and suggestions are welcome.  Please let me know via BugZilla
      
      Thank you!
      c8a0febc
    • Chun-wei Fan's avatar
      VS 2010 support: autotools files updates · 05ee9439
      Chun-wei Fan authored
      The autotools files are updated for the generation of the main gdk-pixbuf
      VS 2010 project (*.vcxproj/*.vcxproj.filters) during "make dist" and to
      ensure the VS2010 project files will be included in the tarball for
      distribution.
      
      The actual VS2010 Project Files will follow shortly.
      05ee9439
    • Chun-wei Fan's avatar
      Added forgotten macro in VS property sheet file · 0bb61771
      Chun-wei Fan authored
      Build qtif support into the main DLL, left this out, oops
      0bb61771
  7. 22 Feb, 2011 1 commit
  8. 15 Feb, 2011 2 commits
  9. 12 Feb, 2011 1 commit
  10. 11 Feb, 2011 3 commits
  11. 07 Feb, 2011 1 commit
  12. 31 Jan, 2011 1 commit
    • Chun-wei Fan's avatar
      Added various items in autotools files · 93a36b05
      Chun-wei Fan authored
      -Added the "build" directory in Makefile.am under SUBDIRS
      -Added the Makefiles to AC_CONFIG_FILES in configure.ac
      
      These will enable Visual C++ 2008 Project Files to be distributed
      during a tarball release
      93a36b05
  13. 26 Jan, 2011 1 commit
  14. 23 Jan, 2011 1 commit
    • Chun-wei Fan's avatar
      Bug 639922: Added distribution stuff for Project Files · 301b8427
      Chun-wei Fan authored
      Added Makefile.am in the new "build" folder and its subfolders so that
      Visual C++ 2008 Project Files can be distributed with make dist once
      the Makefile.am in $(srcroot) has the "build" folder added in the
      SUBDIRS entry
      301b8427
  15. 21 Jan, 2011 2 commits
    • Chun-wei Fan's avatar
      Bug 639922: Readme file for VC++ 2008 · 14d19f6a
      Chun-wei Fan authored
      Oops, I left out the README.txt file that should accompany
      my last commit...sorry.
      14d19f6a
    • Chun-wei Fan's avatar
      Bug 639922: Visual C++ 2008 Project Files · 65cb9548
      Chun-wei Fan authored
      After checking with Tor Lillqvist, these are committed here...
      
      They are done in a similar way to what is now in GLib and GTK+, so that
      if the main GDK-Pixbuf library receives new source files, the new items
      will be added to gdk-pixbuf.vcproj automatically when a tarball is released
      via 'make dist'.
      
      Note that the main GDK-Pixbuf library can be compiled in 2 variants, one
      using the native GDI+ APIs from Windows which is supplied with the Windows
      Platform SDK (but still makes use of LibPNG+ZLib) and another that relies
      on 3rd-party image manipulation libraries (libTIFF, IJG JPEG and libJasPer
      [JPEG-2000 library]) like what is used on other platforms AFAIK.  In either
      case the image loaders are built directly into the main GDK-Pixbuf library
      (i.e. the INCLUDE_<loader> macros are used).
      
      This will build and "install" the main GDK-Pixbuf library and the
      gdk-pixbuf-csource and gdk-pixbuf-query-loaders utility programs.
      65cb9548
  16. 20 Jan, 2011 1 commit
  17. 15 Jan, 2011 1 commit
  18. 13 Jan, 2011 2 commits
  19. 12 Jan, 2011 1 commit
  20. 10 Jan, 2011 1 commit
  21. 29 Dec, 2010 1 commit
  22. 27 Dec, 2010 3 commits
    • Tor Lillqvist's avatar
      Use run-time message catalog directory on Windows · 98d373ed
      Tor Lillqvist authored
      Construct pathname at run-time instead of using a hardcoded
      GDK_PIXBUF_LOCALEDIR.
      
      Should fix bug #634659.
      98d373ed
    • Tor Lillqvist's avatar
      Use the GDI+ loaders by default on Windows · 34cf3df2
      Tor Lillqvist authored
      They have been working nicely for quite some time now.
      
      Also, use a "with" style option for GDI+ instead of an "enable" style
      one, to match the other --with options.
      34cf3df2
    • Tor Lillqvist's avatar
      Use dynamically constructed replacement for GDK_PIXBUF_LIBDIR on Windows · 737e5775
      Tor Lillqvist authored
      Instead of the hardcoded configure- and compile-time GDK_PIXBUF_LIBDIR
      which is not expected to exist at run-time at all, use a pathname
      constructed from where the program binary is, and assuming the normal
      conventions.
      
      This gets used in the --update-cache case to construct the pathname of
      the loaders.cache file.
      
      Note that there already is similar code in main() to construct the
      pathname to where the loader DLLs normally are. There is probably some
      degree of overlap there that could be factored out, but I don't care.
      737e5775
  23. 23 Dec, 2010 2 commits