On 10/9/2021 12:07 AM, Xiang, Haihao wrote:
On Fri, 2021-10-08 at 10:32 -0300, James Almer wrote:
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in
On Fri, 2021-10-08 at 10:32 -0300, James Almer wrote:
> Some packages may not define custom cflags, in which case a simple
> "pkg-config --cflags" call will return an empty string.
> This change will be useful to get a valid include path that can be
> used in library checks.
>
> Signed-off-by: Jam
On 10/8/2021 11:57 AM, Timo Rothenpieler wrote:
On 08.10.2021 15:32, James Almer wrote:
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library ch
On 08.10.2021 15:32, James Almer wrote:
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library checks.
Is that at all a standard thing with pkgc
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library checks.
Signed-off-by: James Almer
---
configure | 5 -
1 file changed, 4 insertions(+
