[cairo] cairo.h in /usr/include

Bill Spitzak spitzak at d2.com
Tue Sep 7 10:29:06 PDT 2004

It seems to me the only purpose of your suggestion is that you want to use 
the -I switch to the compiler to control which version is used. I'm not 
really thrilled with this idea.

Mostly because it requires another -I switch even if I don't change the 

Also, if the interface is not compatable, I have to rewrite my program 
anyway, so I don't see what the difficulty is in changing the name of the 
include file at the same time.

Also you could just change cairo.h to read:

#ifdef CAIRO2
#include "cairo2.h"
#include "cairo1.h"
/* the file cairo1.h contains the old cairo.h */

And then use -DCAIRO2 instead of -I/usr/include/cairo2 as the compiler switch 
to get exactly the same result. I fail to see how this is any harder.

On Sunday 05 September 2004 12:38 pm, Owen Taylor wrote:
> Having cairo.h directly in $(includedir) might be problematical.
> It means you can't have parallel installs of two API incompatible
> versions.

More information about the cairo mailing list