From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH v2] mk: allow exec-env specific targets
Date: Tue, 6 Jun 2017 18:28:36 +0530 [thread overview]
Message-ID: <20170606125836.4789-1-jerin.jacob@caviumnetworks.com> (raw)
In-Reply-To: <20170606063650.31434-1-jerin.jacob@caviumnetworks.com>
Add a hook in generic rte.sdkbuild.mk file
to include exec-env specific targets.
Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
Useful in integrating some custom targets in nonstandard execution environments.
For example, a bare-metal-simulator exec execution environment may need
a target to run the dpdk applications.
v2:
- Change mk/exec-env/$(RTE_EXEC_ENV)/rte.extra.mk to
mk/exec-env/$(RTE_EXEC_ENV)/rte.custom.mk(Thomas)
- Remove empty files and include through -include(Thomas)
---
mk/rte.sdkbuild.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mk/rte.sdkbuild.mk b/mk/rte.sdkbuild.mk
index 0bf909e9e..f6068bb93 100644
--- a/mk/rte.sdkbuild.mk
+++ b/mk/rte.sdkbuild.mk
@@ -38,6 +38,9 @@ else
include $(RTE_SDK)/mk/rte.vars.mk
endif
+# allow exec-env specific targets
+-include $(RTE_SDK)/mk/exec-env/$(RTE_EXEC_ENV)/rte.custom.mk
+
buildtools: | lib
drivers: | lib buildtools
app: | lib buildtools drivers
--
2.13.0
next prev parent reply other threads:[~2017-06-06 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 6:36 [dpdk-dev] [PATCH] " Jerin Jacob
2017-06-06 6:46 ` Thomas Monjalon
2017-06-06 7:02 ` Jerin Jacob
2017-06-06 7:16 ` Thomas Monjalon
2017-06-06 7:50 ` Jerin Jacob
2017-06-06 9:05 ` Jerin Jacob
2017-06-06 9:11 ` Thomas Monjalon
2017-06-06 12:58 ` Jerin Jacob [this message]
2017-07-03 21:17 ` [dpdk-dev] [PATCH v2] " 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=20170606125836.4789-1-jerin.jacob@caviumnetworks.com \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).