From: Nicholas Brown <nickbroon+dpdk@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] pkg-config .pc file for dpdk
Date: Tue, 03 Nov 2015 13:34:28 +0000 [thread overview]
Message-ID: <CA++smEK2wLfR+QDokVPen3Z4HW5a3z4U=_h5B7HegJnPGau_zw@mail.gmail.com> (raw)
Hi,
I've found a couple of mentions of this in the past:
http://dpdk.org/ml/archives/dev/2014-January/001136.html
(discussing having to dpdk app makefiles and having to pass defines as
compiler args)
and:
http://dpdk.org/dev/patchwork/patch/4263/
(discussing providing a .pc for apps to use)
Is anyone working on having dpdk generate a pkg-config .pc file?
For the project I work on, using autotools, to be able to easily use the
PKG_CHECK_MODULES() macro I hacked a simple static .pc file that met my
needs:
prefix=/usr
exec_prefix=${prefix}
libdir=${prefix}/lib
includedir=${prefix}/include
Name: dpdk
Description: dpdk library
Version: 2.0
Libs: -L${libdir} -ldpdk
Cflags: -I${includedir}/dpdk -include
$dpdk_prefix/include/dpdk/rte_config.h -DRTE_MACHINE_CPUFLAG_SSE
-DRTE_MACHINE_CPUFLAG_SSE2 -DRTE_MACHINE_CPUFLAG_SSE3
-DRTE_MACHINE_CPUFLAG_SSSE3
-DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2
,RTE_CPUFLAG_SSE3,RTE_CPUFLAG_SSSE3 -m64 -march=core2
Clearly this not ideal, and it would be better if dpdk generated and
installed a .pc file based build configuration used to generate the
library.
Anyone familiar with dpdk makefiles who can detail what might be needed
to generate the .pc from them?
Cheers,
Nick
reply other threads:[~2015-11-03 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA++smEK2wLfR+QDokVPen3Z4HW5a3z4U=_h5B7HegJnPGau_zw@mail.gmail.com' \
--to=nickbroon+dpdk@gmail.com \
--cc=dev@dpdk.org \
/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).