-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bernhard R. Link wrote: > libcairo2-dev has headers in /usr/include/cairo that > are referenced by itself and by other packages without > the cairo subdirectory thus forcing all programs directly > or indirectly (e.g. gtk) libcairo to include an > -I/usr/include/cairo option. > > This results in: > > * long, unreadable compiler command lines > (which could grow to long for some limited shells, > and causes some people to hide the compiler > command line from the user, which again > make it unnecesarrily difficult to debug > build problems.)
compiler command lines can already be very long - try compiling X or kde or gnome. I don't believe anything you write here is a significant problem. > * breaking programs not using pkgconfig pkg-config is required for developing with cairo, as it is for a lot of other things. pkg-config is required to compile *with* cairo, as it is used by dependent packages too. > Please consider to either (best persuading > upstream, otherwise in the Debian package only) to: > > 1) Move all header files to the place the compiler > would look for them. (i.e. /usr/include) > > 2) Make the compiler look at the proper place, > by changing all #include to <cairo/...>, > telling all users of those file to include > them that way and removing the -I from > cairo.pc to catch all missign places. I am not going to do either of these. The choice cairo made is perfectly acceptable and good, common practice. > In either case, there should finaly be no > -I in the .pc file. (Unless installed by a user > in his home directory, or things like that) > > There are some cases when a -I option might > be necessary, like when upstream forgot to > include the version in the names of the > headers when making an incompatible change > and a Debian package needs to allow installing > thus conflicting versions. libcairo does not > have any such excuse as far as I can see, > as there is only one cairo.h around. I am not convinced by any of your argument. You should use pkg-config and not try to second-guess what compile/link options it generates. Dave -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEIPTDQ+ySUE9xlVoRAkcRAJ948BTPxZH4x4pX0K9ZEcX0HISJrwCfSoox wBsyiFtJHTpVi7ofz2TigMI= =qlZa -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
