From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.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 14:41:27 +0100 [thread overview]
Message-ID: <20170620134127.GA89552@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC359EB177@smartserver.smartshare.dk>
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
>
> Med venlig hilsen / kind regards
> - Morten Brørup
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wiles, Keith
> > Sent: Friday, June 9, 2017 8:06 PM
> > To: Richardson, Bruce
> > Cc: Christian Ehrhardt; Stephen Hemminger; dev
> > Subject: Re: [dpdk-dev] [RFC PATCH] replace DPDK config and build
> > system
> >
> >
> > > On Jun 9, 2017, at 4:05 AM, Bruce Richardson
> > <bruce.richardson@intel.com> wrote:
> > >
> > > On Thu, Jun 08, 2017 at 12:07:05PM -0600, Christian Ehrhardt wrote:
> > >> On Thu, Jun 8, 2017 at 10:26 AM, Stephen Hemminger <
> > >> stephen@networkplumber.org> wrote:
> > >>
> > >>> On a side note, it would be good to use the GCC extensions that
> > >>> allow building different versions of the same routine into one
> > binary.
> > >>>
> > >>
> > >> And we are back to the discussion we had two years ago about how to
> > >> deliver generic yet also optimized binaries in one shot.
> > >> But if the new build system can enable us to do so I'm all in for
> > that.
> > >>
> > >> Thanks for bringing this up in that context Stephen - might be just
> > >> the right time to look at it again.
> > >>
> > > Yep, we can do that. First though, we need to decide what our minimum
> > > supported compiler baseline is going to be.
> > > Also, if the replace the build system, do we want to do a complete
> > > on-shot replacement, or do we want to keep the older one around in
> > > parallel for a while e.g. to support older OS's and compilers.
> >
> > I think it would be a good idea to keep the old version for now.
> >
> > I would suggest adding the new build system to a sandbox repo until we
> > think we have parity then merge into main. Keep the old system in place
> > to allow for other systems until we believe we really have covered all
> > of the bases.
> >
> > What would your baseline be ?
> >
> > I would suggest pick a few distros like Linux Ubuntu, Fedora, Red Hat
> > just a guess at the ones we need to support first.
> >
> > Think we have to support IA and ARM at the same time for the few
> > distros we start with first or at least pick the most used one for ARM
> > first.
> >
> > >
> > > /Bruce
> >
> > Regards,
> > Keith
> >
>
next prev parent reply other threads:[~2017-06-20 13:41 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 [this message]
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=20170620134127.GA89552@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=mb@smartsharesystems.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).