[PATCH xserver] config: declare xserver private dependencies in xorg-server.pc

[Dan Nicholson]

On Thu, Jun 10, 2010 at 8:51 AM, Gaetan Nadon <memsize at videotron.ca> wrote:
> On Thu, 2010-06-10 at 07:01 -0700, Dan Nicholson wrote:
>
> On Thu, Jun 10, 2010 at 6:14 AM, Julien Cristau <jcristau at debian.org> wrote:
>> On Thu, Jun 10, 2010 at 08:54:38 -0400, Gaetan Nadon wrote:
>>
>>> diff --git a/xorg-server.pc.in b/xorg-server.pc.in
>>> index 44f886a..898bed2 100644
>>> --- a/xorg-server.pc.in
>>> +++ b/xorg-server.pc.in
>>> @@ -16,5 +16,6 @@ Name: xorg-server
>>>  Description: Modular X.Org X Server
>>>  Version: @PACKAGE_VERSION@
>>>  Requires: pixman-1 pciaccess xproto >= 7.0.17
>>> +Requires.private: @REQUIRED_MODULES@
>>>  Cflags: -I${sdkdir} @symbol_visibility@
>>>  Libs: -L${libdir}
>>
>> Is all the stuff in REQUIRED_MODULES actually exposed by sdk
>> headers?  AFAICT it's randr, xext, render, input, xkb and xv protos.
>
> Yeah, I'd agree.
>
> Gaeton, maybe you can make a new variable called PC_REQUIRED_MODULES
> or something? This would represent required modules exposed in the
> pkg-config file. For the optional ones, you'd have something like
> this:
>
> if test "x$XV" = xyes; then
>         REQUIRED_MODULES="$REQUIRED_MODULES $VIDEOPROTO"
>         PC_REQUIRED_MODULES="$PC_REQUIRED_MODULES $VIDEOPROTO"
> ...
>
> Sure, will repost. Is the list of sdk exposed modules complete? Is there a
> mechanical way to find out?

I don't know. Julien's list is probably a good start, but probably
someone needs to trawl through the sdk headers and check where the
includes and datatypes come from.

--
Dan