I thought the entire point of the cleanup that Peter did before the Katamari release was to divorce user apps from their reliance on the *proto packages... IE install everything needed to build the applications in the library package rather than the proto package. The proto packages should just contain what the libraries require to communicate with the server.
So for example it looks like xrender.pc says anyone building against libXrender needs to have xrender-proto installed, but I thought that you should just need xrender-proto installed to build libXrender. The problem I'm trying to "solve" is dependency types within MacPorts. If xrender-proto needs to be on the system when an application is building against libXrender, then it needs to be in a different category than if xrender-proto can be pruned after installing libXrender. On Jan 9, 2010, at 13:48, Julien Cristau wrote: > On Sat, Jan 9, 2010 at 13:42:25 -0800, Jeremy Huddleston wrote: > >> Why do the pkg-config files still report that the protos are >> dependencies of the Xlib libraries? Shouldn't that have been removed >> with the big proto/Xlib cleanup prior to the last Katamari? Was this >> just overlooked or intentional? I don't see any reason why a userland >> application building against libX11 should require xproto. >> > I can't see how you could ever build an xlib app without having xproto > installed. For a start, <X11/Xlib.h> needs <X11/Xfuncproto.h> and > <X11/Xosdefs.h>. What problem are you trying to solve? > > Cheers, > Julien
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ xorg-devel mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-devel
