[Mesa-dev] [PATCH] configure: replace pkg-config calls $(PKG_CONFIG) in the makefiles.

[Stéphane Marchesin]

2011/10/3 Matt Turner <mattst88 at gmail.com>:
> 2011/10/3 Stéphane Marchesin <stephane.marchesin at gmail.com>:
>> 2011/10/3 Ian Romanick <idr at freedesktop.org>:
>>> On 10/03/2011 03:59 PM, Stéphane Marchesin wrote:
>>>>
>>>> 2011/10/3 Chad Versace<chad at chad-versace.us>:
>>>>>
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> On 10/03/2011 03:20 PM, Stéphane Marchesin wrote:
>>>>>>
>>>>>> Us poor souls who cross compile mesa want to be able to specify which
>>>>>> pkg-config to pick, or at least just change one place.
>>>>>
>>>>> Would setting PKG_CONFIG_PATH at configuration time solve your problem?
>>>>>
>>>>> When I cross-compile or do other pkg-config hocus pocus, I invoke
>>>>> configure as
>>>>>        ./configure ... PKG_CONFIG_PATH=/my-libdrm/pkgconfig
>>>>>
>>>>
>>>> But that won't override the Makefiles containing hardcoded calls to
>>>> pkg-config, or did I miss something?
>>>
>>> pkg-config is the program, and PKG_CONFIG_PATH tells it where to find the
>>> .pc files.  The program may have a path built into it.  By changing
>>> pkg-config to $(PKG_CONFIG) are you trying to change where it finds the .pc
>>> files, or are you trying to change something else?
>>>
>>
>> In my case, the program is $(TARGET)-pkg-config, so that's not sufficient.
>>
>> Stéphane
>
> This is what I asked about on IRC. I don't understand why the host
> system's pkgconfig binary wouldn't work for you with a suitably set
> PKG_CONFIG_PATH envvar.
>

Our pkg-config wrapper does more than just that. It does, among other
things, set PKG_CONFIG_PATH and call pkg-config.

> configs/autoconf.in should be updated as well, I think.
>

As far as I can see, it should include configs/default.

Stéphane