[cairo] Re: Cairographics on win32
stuartp at gmail.com
Thu Apr 7 16:46:10 PDT 2005
I really think that checking in Visual Studio projects is the wrong
thing to do here. We should just create a windows makefile that you
can use nmake to build, similarly to what glib, pango, etc do.
On Apr 7, 2005 4:20 PM, Oleg Smolsky
<oleg.smolsky at pacific-simulators.co.nz> wrote:
> Hello Carl,
> Carl Worth wrote on Friday, 8 April 2005:
> >> Sure, I can make everything ANSI C compliant. In any case, I've just
> >> checked, and the only macros I really need are
> >> CAIRO_HAS_WIN32_FONT=1
> >> CAIRO_HAS_WIN32_SURFACE=1
> >> and they are defined inside my .vcproj.
> >> Actually, IMHO, they should be in packaging/msvc/cairo-features.h
> >> which should be included really really early by every .c file......
> > Yes.
> Alright, these are now in my (win32/vc)-specific cairo-features.h, and
> I have removed them from the .vcproj. Less hidden pre-processor shite.
> > As for advertising features that aren't present, what I think we
> > should do is always define all the macros, but with either a true or
> > false value
> Done. And I have also changed a few #ifdefs to #ifs :)
> > I concede as far as the Xlib backend on win32 goes. I would like the
> > PS/PDF backends to be built by default on pretty much all systems, but
> > it sounds like we've still got some more work to do on those backends
> > before they are ready for that.
> Yeah.... There is also a bigger question here - external dependencies.
> Say, png stuff depends on libpng and zlib that are available with
> .vcproj-ects. So, a developer can easily get them, while some pdf/ps
> dependencies are no that easy of obtain.
> Anyway, here is patch3.
> Best regards,
> cairo mailing list
> cairo at cairographics.org
More information about the cairo