<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-text-flowed" style="font-family: -moz-fixed; font-size: 14px;" lang="x-unicode">(Sorry for the resend-I mailed to the list from my other [non-subscribed] e-mail account by accident) Hi, I have come up with Visual C++ project files to build Cairo (and optionally Cairo-GObject) on Windows using Visual C++ 2008/2010 (Express or better) under Win32(x86) and x64 modes. This project file set will eliminate the need to install mozilla-build for Windows to build with Visual C++. Cairo is built with the following features, only requiring Visual C++ itself, the Windows/Platform SDK and LibPNG and ZLib to build unless optional features are required for the build: CAIRO_HAS_WIN32_SURFACE CAIRO_HAS_WIN32_FONT CAIRO_HAS_PNG_FUNCTIONS CAIRO_HAS_IMAGE_SURFACE CAIRO_HAS_PS_SURFACE CAIRO_HAS_PDF_SURFACE CAIRO_HAS_SVG_SURFACE CAIRO_HAS_SCRIPT_SURFACE CAIRO_HAS_TEE_SURFACE CAIRO_HAS_XML_SURFACE CAIRO_HAS_FT_FONT (optional) CAIRO_HAS_FC_FONT (optional) CAIRO_HAS_GL_SURFACE (optional) CAIRO_HAS_WGL_FUNCTIONS (optional) CAIRO_HAS_GOBJECT_FUNCTIONS (optional) The project files are done in a way similar to what is now done for the Visual C++ 2008/2010 project files for the GTK+ stack, which I also maintain. This means that the source file listings are filled into the project files during "make dist", so additions and removals of source files will only need to be done to src/Makefile.sources (for Cairo) and/or util/cairo-gobject/Makefile.am (for Cairo-GObject), as what is done now AFAIK, which will greatly simplify maintenance of the Visual C++ Project files. Please let me know of any comments or suggestions about these project files. With blessings, Thank you! </div> </body> </html>