Re: [xslt] [patch] 'plugins' variable for libxslt.pc
- From: Tony Graham <Tony Graham MenteithConsulting com>
- To: xslt gnome org
- Subject: Re: [xslt] [patch] 'plugins' variable for libxslt.pc
- Date: Tue, 21 Aug 2007 14:36:55 +0100
On Tue, Aug 21 2007 13:14:08 +0100, veillard redhat com wrote:
> On Tue, Aug 21, 2007 at 10:47:53AM +0100, Tony Graham wrote:
>> The following patch lets:
>>
>> pkg-config --variable=plugins libxslt
>>
>> return the same plugin location as does:
>>
>> xslt-config --plugins
> [...]
>> ===================================================================
>> --- libxslt.pc.in (revision 1435)
>> +++ libxslt.pc.in (working copy)
>> @@ -3,6 +3,7 @@
>> libdir= libdir@
>> includedir= includedir@
>>
>> +plugins= LIBXSLT_DEFAULT_PLUGINS_PATH@
>>
>> Name: libxslt
>> Version: @VERSION@
>
> Hum, I assume this means the plugin directory get exported as a variable
> for pkg-config after this patch, right ?
The value would be hardcoded into the generated 'libxslt.pc' when you
run 'configure' before building libxslt, just as it is hardcoded into
the generated 'xslt-config'.
Someone used to using pkg-config in configure.in files could use
'pkg-config --variable=plugins libxslt' in their configure.in for a
plugin project to get the directory in which to install their plugin
rather than going to xslt-config for the one extra piece of information
they can't currently get from pkg-config.
Regards,
Tony Graham.
======================================================================
Tony Graham MenteithConsulting com http://www.menteithconsulting.com
Menteith Consulting Ltd Registered in Ireland - No. 428599
Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
----------------------------------------------------------------------
Menteith Consulting -- Understanding how markup works
======================================================================
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]