From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC PATCH] build for DPDK with meson and ninja
Date: Thu, 8 Jun 2017 12:50:38 +0530 [thread overview]
Message-ID: <ca3dd199-b258-8a7d-7d99-34f9ca06612e@nxp.com> (raw)
In-Reply-To: <20170607104743.275149-2-bruce.richardson@intel.com>
Hello Bruce,
On Wednesday 07 June 2017 04:17 PM, Bruce Richardson wrote:
> to use, need to have meson >= 0.4 and ninja-build packages installed.
>
> Then do the following in main DPDK directory:
>
> meson build
> cd build
> ninja
> sudo ninja install
>
> This will compile up some DPDK libs, the FVL PMD and testpmd and install
> them in /usr/local/. [On Fedora you will need to add /usr/local/lib64 to
> your ld path, it's not there by default.]
> Then you can run testpmd as e.g.
>
<...snip...>
> diff --git a/test/test/meson.build b/test/test/meson.build
> new file mode 100644
> index 0000000..cc85408
> --- /dev/null
> +++ b/test/test/meson.build
> @@ -0,0 +1,23 @@
> +executable('dpdk-test',
> + sources: [
> + 'commands.c',
> + 'packet_burst_generator.c',
> + 'test.c',
> + 'test_acl.c',
> + 'test_cmdline.c',
> + 'test_cmdline_cirbuf.c',
> + 'test_cmdline_etheraddr.c',
> + 'test_cmdline_ipaddr.c',
> + 'test_cmdline_lib.c',
> + 'test_cmdline_num.c',
> + 'test_cmdline_portlist.c',
> + 'test_cmdline_string.c',
> + 'test_cpuflags.c',
> + 'test_mp_secondary.c',
> + 'test_pmd_perf.c',
> + 'test_ring.c',
> + 'test_ring_perf.c'
> + ],
> + dependencies: [rte_eal, rte_ring, rte_mempool, rte_cmdline,
> + rte_mbuf, rte_net, rte_ether, rte_acl],
> + install: true)
<..snip..>
I tried this with x86 and it worked like a charm. Really nice and clean
way to build DPDK - and super fast. Awesome.
I want to use this for an ARM target. Any idea what I should change in
meson.build? Or, is that even straightforward?
(Yes, I can lookup documentation for meson - just being lazy. If you
don't have much idea, I will give this a spin on ARM in a couple of
days)
-
Shreyansh
next prev parent reply other threads:[~2017-06-08 7:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 10:47 [dpdk-dev] [RFC PATCH] replace DPDK config and build system Bruce Richardson
2017-06-07 10:47 ` [dpdk-dev] [RFC PATCH] build for DPDK with meson and ninja Bruce Richardson
[not found] ` <CGME20170607143643eucas1p10bce80dca22034efc6402d5944a6a0ed@eucas1p1.samsung.com>
2017-06-07 14:36 ` [dpdk-dev] [dpdk-dev,RFC] " Ilya Maximets
2017-06-07 14:51 ` Bruce Richardson
2017-06-07 18:12 ` [dpdk-dev] [RFC PATCH] " Jerin Jacob
2017-06-08 8:43 ` Bruce Richardson
2017-06-08 7:20 ` Shreyansh Jain [this message]
2017-06-08 8:48 ` Bruce Richardson
2017-06-07 13:08 ` [dpdk-dev] [RFC PATCH] replace DPDK config and build system Van Haaren, Harry
[not found] ` <1496841784.25214.6.camel@gmail.com>
2017-06-07 13:27 ` Bruce Richardson
2017-06-07 23:26 ` Stephen Hemminger
2017-06-08 8:59 ` Bruce Richardson
2017-06-08 16:26 ` Stephen Hemminger
2017-06-08 18:07 ` Christian Ehrhardt
2017-06-08 18:21 ` Wiles, Keith
2017-06-09 9:05 ` Bruce Richardson
2017-06-09 18:06 ` Wiles, Keith
2017-06-20 13:34 ` Morten Brørup
2017-06-20 13:41 ` Bruce Richardson
2017-06-20 14:25 ` Morten Brørup
2017-06-20 14:43 ` Bruce Richardson
2017-06-22 17:14 ` Neil Horman
2017-06-22 20:27 ` Bruce Richardson
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=ca3dd199-b258-8a7d-7d99-34f9ca06612e@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=bruce.richardson@intel.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).