From: Ye Xiaolong <xiaolong.ye@intel.com> To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> Cc: Thomas Monjalon <thomas@monjalon.net>, John McNamara <john.mcnamara@intel.com>, Marko Kovacevic <marko.kovacevic@intel.com>, dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>, Stephen Hemminger <stephen@networkplumber.org> Subject: Re: [dpdk-dev] [PATCH v5] doc: introduce openwrt how-to guide Date: Mon, 17 Feb 2020 14:21:53 +0800 Message-ID: <20200217062152.GC60672@intel.com> (raw) In-Reply-To: <20200217061241.6661c175@Sovereign> On 02/17, Dmitry Kozlyuk wrote: >> On 02/16, Thomas Monjalon wrote: >> >16/02/2020 18:29, Ye Xiaolong: >> >> On 02/16, Thomas Monjalon wrote: >> >> >18/01/2020 06:48, Xiaolong Ye: >> >> >[...] >> >> >> + [binaries] >> >> >> + c = 'x86_64-openwrt-linux-gcc' >> >> >> + cpp = 'x86_64-openwrt-linux-cpp' >> >> >> + ar = 'x86_64-openwrt-linux-ar' >> >> >> + strip = 'x86_64-openwrt-linux-strip' >> >> >> + >> >> >> + meson builddir --cross-file openwrt-cross >> >> > >> >> >This is really a good example why meson should allow to override the toolchain prefix. >> >> >> >> Not sure whether I get your point or not, do you mean meson should support >> >> something like "cross = 'x86_64-openwrt-linux-'" in config file (just like the >> >> CROSS_COMPILE for make build system), so we don't need to override the build >> >> tools one by one? >> > >> >Yes, I think meson should support CROSS_COMPILE environment variable >> >or a similar config option. I don't see the point of creating a new >> >config file for each toolchain prefix. >> >> Totally agree, I would try to work on this to make it happen. > >You might be interested in this PR and its discussion: >https://github.com/mesonbuild/meson/pull/5859 Thanks for the info, I'll look into it. Thanks, Xiaolong > >-- >Dmitry Kozlyuk
next prev parent reply other threads:[~2020-02-17 6:23 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-29 8:19 [dpdk-dev] [PATCH] " Xiaolong Ye 2019-11-29 10:09 ` Bruce Richardson 2019-11-29 15:03 ` Ye Xiaolong 2019-11-29 16:59 ` Stephen Hemminger 2019-12-01 11:30 ` Ye Xiaolong 2019-12-02 6:34 ` [dpdk-dev] [PATCH v2] " Xiaolong Ye 2019-12-02 7:31 ` Jerin Jacob 2019-12-02 8:09 ` Ye Xiaolong 2019-12-12 2:25 ` [dpdk-dev] [PATCH v3] " Xiaolong Ye 2019-12-16 3:01 ` [dpdk-dev] [PATCH v4] " Xiaolong Ye 2019-12-19 6:05 ` Zhang, Xiao 2020-01-17 13:46 ` Mcnamara, John 2020-01-18 1:52 ` Ye Xiaolong 2020-01-18 5:48 ` [dpdk-dev] [PATCH v5] " Xiaolong Ye 2020-01-22 12:34 ` Mcnamara, John 2020-02-16 11:04 ` Thomas Monjalon 2020-02-16 17:29 ` Ye Xiaolong 2020-02-16 18:02 ` Thomas Monjalon 2020-02-17 1:18 ` Ye Xiaolong 2020-02-17 3:12 ` Dmitry Kozlyuk 2020-02-17 6:21 ` Ye Xiaolong [this message] 2020-02-17 2:47 ` [dpdk-dev] [PATCH v6] " Xiaolong Ye 2020-02-17 15:08 ` Ray Kinsella 2020-02-17 15:44 ` Ye Xiaolong 2020-02-17 15:49 ` Ray Kinsella 2020-02-18 8:26 ` Mcnamara, John 2020-02-18 9:12 ` Ray Kinsella 2020-02-18 9:32 ` Thomas Monjalon 2020-02-18 9:49 ` Ye Xiaolong 2020-02-18 10:08 ` Ray Kinsella 2020-02-21 21:08 ` Thomas Monjalon
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=20200217062152.GC60672@intel.com \ --to=xiaolong.ye@intel.com \ --cc=bruce.richardson@intel.com \ --cc=dev@dpdk.org \ --cc=dmitry.kozliuk@gmail.com \ --cc=john.mcnamara@intel.com \ --cc=marko.kovacevic@intel.com \ --cc=stephen@networkplumber.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
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git