DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>,
	"Christian Ehrhardt" <christian.ehrhardt@canonical.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"dev" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC PATCH] replace DPDK config and build system
Date: Tue, 20 Jun 2017 16:25:12 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC359EB17A@smartserver.smartshare.dk> (raw)
In-Reply-To: <20170620134127.GA89552@bricha3-MOBL3.ger.corp.intel.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, June 20, 2017 3:41 PM
> To: Morten Brørup
> Cc: Wiles, Keith; Christian Ehrhardt; Stephen Hemminger; dev
> Subject: Re: [dpdk-dev] [RFC PATCH] replace DPDK config and build
> system
> 
> On Tue, Jun 20, 2017 at 03:34:58PM +0200, Morten Brørup wrote:
> > FYI: We are using Crosstool-NG (http://crosstool-ng.github.io/). It
> seems to be quite popular for cross compiling.
> >
> 
> How does a tool like that interact with build-systems then - either
> with our current one, or with a hypothetical future one using
> meson+ninja as below? Does it simplify what needs to be provided in the
> build config tool?
> 
> /Bruce

The main purpose of our build-system is to be able to just type "make" to build everything in our project (including the cross compiler itself). The purpose is not to simplify the build config tool for each of the libraries and executables in our project.

Please note that standardization is a benefit in itself! If every 3rd party library and executable in a complex project like ours had completely different build-systems, it would be a nightmare for us to maintain our project.

And to answer your question: Basically when using cross-tools, we set up a bunch of environment variables and then call the Makefile of each library and executable in the project (to configure and/or compile them). These environment variables are somewhat standardized, so modifying a Makefile for a 3rd party library/executable that is not designed for cross compiling is only a minor pain, not a major pain. I haven't looked at meson+ninja, but from reading the discussion here, it seems somewhat similar.

If DPDK switches to meson+ninja we will make it work for us too, so I'm not opposing such a change. I only wanted to highlight that Crosstool-NG is a very popular cross compiling environment, and has a good track record in this area.


Med venlig hilsen / kind regards
- Morten Brørup




  reply	other threads:[~2017-06-20 14:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 10:47 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
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 [this message]
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=98CBD80474FA8B44BF855DF32C47DC359EB17A@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=stephen@networkplumber.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).