From: Neil Horman <nhorman@tuxdriver.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/5] examples: add a new makefile to build all examples
Date: Fri, 25 Apr 2014 10:05:26 -0400 [thread overview]
Message-ID: <20140425140526.GG14074@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1398427249-15418-1-git-send-email-olivier.matz@6wind.com>
On Fri, Apr 25, 2014 at 02:00:44PM +0200, Olivier Matz wrote:
> This patch series adds a makefile to build all examples supported
> by the configuration. It helps to check that all examples compile
> after a dpdk modification.
>
> After applying the patches, it is possible to build all examples by doing
> the following:
>
> user@droids:~/dpdk.org$ cd examples
> user@droids:~/dpdk.org/examples$ make RTE_SDK=${PWD}/.. \
> RTE_TARGET=x86_64-default-linuxapp-gcc
What you actually want here is RTE_TARGET=build, as the Makefile looks for the
${RTE_TARGET}/.config file, it doesn't just parse whatever target file you
specify.
That begs the bigger point, RTE_TARGET will always be =build, so why not just
add a top level make rule for the examples subdirectory, then RTE_SDK and
RTE_TARGET will just be automatically set.
Regards
Neil
next prev parent reply other threads:[~2014-04-25 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 12:00 Olivier Matz
2014-04-25 12:00 ` [dpdk-dev] [PATCH 1/5] mk: introduce rte.extsubdir.mk Olivier Matz
2014-04-25 12:00 ` [dpdk-dev] [PATCH 2/5] examples: use rte.extsubdir.mk to process subdirectories Olivier Matz
2014-04-25 12:00 ` [dpdk-dev] [PATCH 3/5] examples: add a makefile to build all examples Olivier Matz
2014-04-25 12:00 ` [dpdk-dev] [PATCH 4/5] examples: fix qos_sched makefile Olivier Matz
2014-04-25 12:00 ` [dpdk-dev] [PATCH 5/5] examples: fix netmap_compat example Olivier Matz
2014-04-25 14:05 ` Neil Horman [this message]
2014-04-25 16:24 ` [dpdk-dev] [PATCH 0/5] examples: add a new makefile to build all examples Olivier MATZ
2014-04-25 18:39 ` Neil Horman
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=20140425140526.GG14074@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.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).