From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] devtools/test-meson-builds: allow custom set of examples
Date: Thu, 12 Nov 2020 15:40:59 +0100 [thread overview]
Message-ID: <CAJFAV8yGUNUq1Ng0ouMXuzoydEbhLZjiLyv+ZPJjGAnKV+XZmw@mail.gmail.com> (raw)
In-Reply-To: <4260818.77I6s4UBcg@thomas>
On Tue, Nov 10, 2020 at 3:36 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> PKG_CONFIG_PATH=../dpdk-build/build-x86-default/meson-private \
> pkg-config --define-prefix --libs-only-L libdpdk
> -L/usr/local/lib
>
> Oh! I am testing on the build directory instead of installed one.
>
> PKG_CONFIG_PATH=../dpdk-build/build-x86-default/install/usr/local/lib/pkgconfig \
> pkg-config --define-prefix --libs-only-L libdpdk
> -L../dpdk-build/build-x86-default/install/usr/local/lib
>
> Good :)
> Now THE question: what is the difference between these two .pc files?
I moved libdpdk{,-libs}.pc files in different folders.
pkg-config seems to check the path to the .pc files to decide what to return.
There seems to be a combination of having $prefix in the path and
/pkgconfig as the last directory.
--
David Marchand
prev parent reply other threads:[~2020-11-12 14:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 17:38 Bruce Richardson
2020-11-09 10:01 ` David Marchand
2020-11-12 15:40 ` Thomas Monjalon
2020-11-09 17:09 ` Thomas Monjalon
2020-11-09 18:02 ` Bruce Richardson
2020-11-09 19:26 ` Thomas Monjalon
2020-11-10 10:08 ` Bruce Richardson
2020-11-10 11:25 ` Thomas Monjalon
2020-11-10 11:34 ` Bruce Richardson
2020-11-10 13:04 ` Thomas Monjalon
2020-11-10 13:19 ` Bruce Richardson
2020-11-10 13:53 ` Thomas Monjalon
2020-11-10 14:19 ` Bruce Richardson
2020-11-10 14:36 ` Thomas Monjalon
2020-11-12 14:40 ` David Marchand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJFAV8yGUNUq1Ng0ouMXuzoydEbhLZjiLyv+ZPJjGAnKV+XZmw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).