On Sun, Dec 13, 2009 at 21:45:06 -0500, Dave Witbrodt wrote: > One last issue to mention -- probably nothing to worry about, since I am > a noob to Mesa and to building DEBs. I noticed that after the "install" > target of 'debian/rules' is run, there are two copies of a file called > 'gl.pc': one is in 'debian/tmp/usr/lib/glx/pkgconfig' and the other is > in 'debian/tmp/usr/lib/pkgconfig'. Only one ends up being packaged -- > the one build by the software rasterization config -- while the version > created by the "dri" config is left unused. > > Now I don't truly understand what gl.pc is for but, as far as I have > been able to gather, it is is used by 'pkg-config' to determine > dependency information about libraries installed on the build system. > Won't 'pkg-config' get confused if I want to build software against a > DRI version of libGL.so, but the installed gl.pc contains dependency > information about a (completely different) software rasterizing version > of libGL.so? > > I have to plead ignorance here, and I am literally just seeking to > satisfy my curiosity about this. The man page for 'pkg-config' > indicates that more than one *.pc file can be used in a system for very > similar libraries, so I was just wondering if it would be better to use > both copies of gl.pc somehow. > All of the libGLs have to be compatible, so any difference between those .pc files shouldn't matter.
Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
