[PATCH] weston.pc: Added libexecdir and pkglibexecdir variables
Eduardo Lima (Etrunko)
eduardo.lima at linux.intel.com
Mon Jun 10 10:40:19 PDT 2013
On 06/07/2013 11:01 AM, Pekka Paalanen wrote:
> On Mon, 3 Jun 2013 12:24:09 -0300
> "Eduardo Lima (Etrunko)" <eduardo.lima at linux.intel.com> wrote:
>
>> From: "Eduardo Lima (Etrunko)" <eduardo.lima at intel.com>
>>
>> These can be used by external clients to check the installation path
>>
>> Signed-off-by: Eduardo Lima (Etrunko) <eduardo.lima at intel.com>
>> ---
>> src/weston.pc.in | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/src/weston.pc.in b/src/weston.pc.in
>> index 537cc89..828cb1f 100644
>> --- a/src/weston.pc.in
>> +++ b/src/weston.pc.in
>> @@ -2,6 +2,8 @@ prefix=@prefix@
>> exec_prefix=@exec_prefix@
>> libdir=@libdir@
>> includedir=@includedir@
>> +libexecdir=@libexecdir@
>> +pkglibexecdir=${libexecdir}/@PACKAGE@
>>
>> Name: Weston Plugin API
>> Description: Header files for Weston plugin development
>
> Right, I wonder if there is more fix here.
>
> $ pkg-config --variable=libexecdir weston
> /home/pq/local/libexec
> $ pkg-config --variable=pkglibexecdir weston
> /home/pq/local/libexec/weston
>
> My prefix=/home/pq/local.
>
> But it seems weston installs all programs into libexecdir, not
> pkglibexecdir. Should weston install them to pkglibexecdir instead?
> Or why add pkglibexecdir?
>
I have added the pkglibexedir in an attempt to avoid crowding libexecdir
too much. Other than that, no special reason.
--
Eduardo de Barros Lima (Etrunko)
Software Engineer, Open Source Technology Center
Intel Corporation
São Paulo, Brazil
eduardo.lima at linux.intel.com
More information about the wayland-devel
mailing list