Bug 4262

Created attachment 3058 [details] [review]
Simple solution, reverting to 0.9.3 version  of cairo.pc.in

Simple solution, converting cairo.pc.in to it's 0.9.3 version

Forgot to mention, the bug is in 1.0.0 not in 0.9.3, unfortunately a 1.0.0 field
doesn't exist yet. :)

Sorry about the missing version in the bugzilla interface. Added 1.0.0
now and moved the bug there.

We intentionally don't want the libraries for FreeType to be given
when you do pkg-config --libs cairo to avoid bringing in unnecessary
library dependencies, and without the libraries the cflags don't
do much good ... you still can't make use of the functions in 
cairo-ft.h, since they are

It might make sense to add a cairo-ft.pc that pulled in the libraries
and cflags for freetype and fontconfig. On the other hand, it doesn't
really have much benefits beyond:

 pkg-config --cflags cairo fontconfig

I think there would some significant benefit to cairo-ft.pc.

The benefit would be in increased guessability. A strong correlation
between header file names used in #include directives and pkg-config
package names could go quite a ways at making things feel very robust
I think.

The other major benefit of cairo-ft.pc would be that it ensures cairo is
compiled with fc support.  No more custom configure tests.

Cooking patches.

I pushed a commit in my repo that adds per-backend pkg-config files.  Carl will
push it into the next snapshot.