<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Wed, 2010-06-09 at 23:48 +0200, Julien Cristau wrote: <BLOCKQUOTE TYPE=CITE> <PRE> On Wed, Jun 9, 2010 at 17:42:00 -0400, Gaetan Nadon wrote: > On Wed, 2010-06-09 at 23:24 +0200, Julien Cristau wrote: > > > On Wed, Jun 9, 2010 at 17:17:44 -0400, Gaetan Nadon wrote: > > > > > The xf86.h file contains external declarations specific to RANDR > > > If this extension is defined (installed) evdev will not compile > > > if randrproto is not installed. > > > Because this is an optional extension, XORG_DRIVER_CHECK_EXT > > > must be used. > > > > > If the only thing pulling in randr headers is xf86.h then the dependency > > on randrproto should come from xorg-server.pc, not from evdev. > > > > The protocols are independent packages which can be removed/uninstalled > at any time. I simply go to proto/randrproto and "make uninstall". Then > evdev fails to compile. Same issue with xext and kbproto. The xf86.h > file is "for video driver" according to it's own comment. > > I would love for this dependency not to exist. I originally thought it > did not. > I'm not sure what you're getting at, but that has nothing to do with what I said afaict. I'm saying 'Requires.private: randrproto' in xorg-server.pc would be the correct way to express the fact that xf86.h needs randrproto.h. </PRE> </BLOCKQUOTE> Now I get it. However randr is an optional extension, it may or may not be defined in the server. On the other hand, the server should perhaps have this in place for xext, kbproto and inputproto which are part of the server and not optional. This is an interesting path...<BR> <BR> <BLOCKQUOTE TYPE=CITE> <PRE> Cheers, Julien </PRE> </BLOCKQUOTE> </BODY> </HTML>