Re: [PATCH] Make pkg-config files cross-compile friendly - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Make pkg-config files cross-compile friendly
Date
Msg-id b47c8273-5e19-f9f5-cc7f-fd63edad8304@enterprisedb.com
Whole thread Raw
In response to [PATCH] Make pkg-config files cross-compile friendly  (Sebastian Kemper <sebastian_ml@gmx.net>)
List pgsql-hackers
On 05.03.20 22:38, Sebastian Kemper wrote:
> This commit addresses this by doing the following two things:
> 
>    1. Instead of hard coding the paths in "Cflags" and "Libs"
>       "${includedir}" and "${libdir}" are used. Note: these variables can
>       be overriden on the pkg-config command line
>       ("--define-variable=libdir=/some/path").
> 
>    2. Add the variables "prefix" and "exec_prefix". If "includedir"
>       and/or "libdir" are using these then construct them accordingly.
>       This is done because buildroots (for instance OpenWrt) tend to
>       rename the real pkg-config and call it indirectly from a script
>       that sets "prefix", "exec_prefix" and "bindir", like so:

Committed.  I simplified your code a little bit, and I also made it so 
that exec_prefix is set to ${prefix} by default.  That way it matches 
what most other .pc files I have found do.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add guc to enable send SIGSTOP to peers when backend exits abnormally
Next
From: Bharath Rupireddy
Date:
Subject: Re: Trap errors from streaming child in pg_basebackup to exit early