[cairo] [PATCH] OS/2 backend support files

[Peter Weilbacher]

Jonathon Jongsma wrote:
> On 8/8/06, Peter Weilbacher <mozilla at weilbacher.org> wrote:
>> Well, the "solution" for me was that I managed to install pkg-config on
>> OS/2 and tinker with the respective .pc files until I got configure to
>> run through.
>>
>> But actually, there has to be another way to make the _{CFLAGS,LIBS}
>> variables consistently uppercased, because ./configure --help lists lots
>> of other variables that are all uppercase, too (POPPLER_* and FREETYPE_*
>> for example). I think I understand too little of autoconf to determine
>> why it works for them but not for png_* and xlib_xrender_*.
>>
> 
> If I'm not mistaken, it's simply because the pkg-config checks are
> written that way.  Take a look at the following snippets from
> configure.in
> 
> PKG_CHECK_MODULES(POPPLER, poppler-glib >= 0.4.1 pango gtk+-2.0,
> [test_pdf=yes], [test_pdf=no])
> 
> Notice the first argument to PKG_CHECK_MODULES is capitalized.  now
> take a look at the png check:
> 
> PKG_CHECK_MODULES(png, $png_REQUIRES)
> 
> Notice the first argument is lowercased.  The PKG_CHECK_MODULES macro
> uses the first argument to construct the variables by just appending
> _LIBS or _CFLAGS to them.  I don't know if there's another reason why
> the 'png' can't be upper-cased here, but you might try playing around
> with it.

Yes, that I understood. But Behdad rightfully remarked that for PNG this
wouldn't work as the CAIRO_BACKEND_ENABLE macro makes use of the
variable in another way that was not immediately obvious to me at the
beginning. If one just uppercases PNG in the PKG_CHECK_MODULES line, the
check will be broken (that was the patch that I sent around about a week
ago).

   Peter.