From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier MATZ <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] mk: rule help
Date: Fri, 17 May 2013 17:27:29 +0200 [thread overview]
Message-ID: <201305171727.30089.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <5195F309.1080101@6wind.com>
17/05/2013 11:06, Olivier MATZ :
> On 05/07/2013 05:17 PM, Thomas Monjalon wrote:
> > The macro maketxt allow to interpret syntax "# make foo" while keeping
> > indentation of the source document.
> > Here, it is used to call "make showconfigs" to list available targets.
> [..]
> > +define maketxt
> > + sed 's,^\([[:space:]]*\)# make \(.*\),make -rRs \2 | sed "s/^/\1/",e' $1
> > +endef
>
> I think the "maketxt" macro is overkill... why not just a "cat" ?
Because the syntax "# make" is interpreted.
With build-sdk-quick.txt, it lists all available configurations.
Maybe I should add a comment before the macro to explain it.
--
Thomas
next prev parent reply other threads:[~2013-05-17 15:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 15:17 [dpdk-dev] [PATCH 0/3] make help Thomas Monjalon
2013-05-07 15:17 ` [dpdk-dev] [PATCH 1/3] mk: rule showconfigs for configs listing Thomas Monjalon
2013-05-17 9:05 ` Olivier MATZ
2013-05-17 14:53 ` Thomas Monjalon
2013-05-07 15:17 ` [dpdk-dev] [PATCH 2/3] doc: how to build Thomas Monjalon
2013-05-17 9:06 ` Olivier MATZ
2013-05-17 15:20 ` Thomas Monjalon
2013-05-07 15:17 ` [dpdk-dev] [PATCH 3/3] mk: rule help Thomas Monjalon
2013-05-17 9:06 ` Olivier MATZ
2013-05-17 15:27 ` Thomas Monjalon [this message]
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 0/3] make help Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 1/3] doc: how to build Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 2/3] mk: rule showconfigs for configs listing Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 3/3] mk: rule help Thomas Monjalon
2013-05-30 14:55 ` [dpdk-dev] [PATCH v2 0/3] make help Olivier MATZ
2013-05-30 22:02 ` 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=201305171727.30089.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
/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).