[cairo] [cairo-announce] cairo release 1.2.2 now available

[Tor Lillqvist]

Carl Worth writes:
 > A new cairo release 1.2.2 is now available from:
 > 
 >         http://cairographics.org/releases/cairo-1.2.2.tar.gz

There is a problem in the configure.in and thus the included
pregenerated configure script: The CAIRO_BACKEND_ENABLE macro calls
for ps, pdf and svg are broken:

CAIRO_BACKEND_ENABLE(ps, PostScript, ps, PS_SURFACE, auto, [], [
  if test x"$have_ft_load_sfnt_table" != "xyes" ; then
...

CAIRO_BACKEND_ENABLE(pdf, PDF, pdf, PDF_SURFACE, auto, [], [
  if test x"$have_ft_load_sfnt_table" != "xyes" ; then
...

CAIRO_BACKEND_ENABLE(svg, SVG, svg, SVG_SURFACE, auto, [], [
  if test x"$have_ft_load_sfnt_table" != "xyes" ; then
...

Note there is an empty string [] passed as the sixth parameter, and
then a shell command sequence passed as seventh parameter. Presumably
that command sequence is supposed to be the $6, as described in the
doc for CAIRO_BACKEND_ENABLE. $7 isn't used at all by
CAIRO_BACKEND_ENABLE, so the command sequences passed here don't end
up anywhere in the configure script at all, which means that the
linking phase fails on Win32 at least due to the missing -lz.

However, changing that and re-autoconfing then causes the PDF backend
not to be enabled on Win32 if freetype wasn't found, contrary to what
the release announcement said...

Is it possible to build cairo for Win32 with pdf but without freetype
only using some other build mechanism than the configure script?

Also, a copy/paste error in the call to CAIRO_BACKEND_ENABLE(pdf,...),
the commands set use_ps (and not use_pdf) if zlib isn't found.

BTW, is there any general consensus on whether the cairo Win32
binaries that are distributed on ftp.gtk.org should use freetype and
fontconfig or not (once it actually is possible to have pdf but not
freetype)? Does anyone care, or do those who care build cairo on Win32
themselves anyway?

--tml