DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] drivers: improve pmdinfo generation when using meson
Date: Tue, 30 Jan 2018 15:07:11 +0000	[thread overview]
Message-ID: <20180130150710.GA25924@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20180125111443.231999-1-bruce.richardson@intel.com>

On Thu, Jan 25, 2018 at 11:14:43AM +0000, Bruce Richardson wrote:
> Since meson 0.44, changing any file inside a PMD directory (quite
> correctly) triggers a full re-run of meson on build, rather than an
> incremental build as with earlier versions. This rerun is needed because
> we use "grep" in meson to search for files on which to run pmdinfogen, and
> changing any of those files means that grep and, therefore meson, needs to
> be rerun. [Previous versions of meson did not track this dependency on the
> grep command, and so did incremental builds only.]
> 
> If, however, we take advantage of pmdinfogen's ability to use stdin and
> stdout instead of files, we can instead use a shell script to process an
> entire static archive and generate a single .c file from it. This
> eliminates the need for grep, and means that changes to a PMD file only
> need an incremental build - a significant time saving.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
Applied to dpdk-next-build

/Bruce

      reply	other threads:[~2018-01-30 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 11:14 Bruce Richardson
2018-01-30 15:07 ` Bruce Richardson [this message]

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=20180130150710.GA25924@bricha3-MOBL3.ger.corp.intel.com \
    --to=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).