Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 14/15] tools/sppc: add helper script for build
Date: Fri, 15 Jun 2018 17:37:53 +0900	[thread overview]
Message-ID: <20180615083754.20220-15-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180615083754.20220-1-ogawa.yasufumi@lab.ntt.co.jp>

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

'build/run.sh' is a helper script to inspect inside the container.
You can run bash on the container to confirm behaviour of targetting
application, or run any of command.

Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
 tools/sppc/build/run.sh | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100755 tools/sppc/build/run.sh

diff --git a/tools/sppc/build/run.sh b/tools/sppc/build/run.sh
new file mode 100755
index 0000000..ace7ee8
--- /dev/null
+++ b/tools/sppc/build/run.sh
@@ -0,0 +1,34 @@
+#!/bin/bash
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2018 Nippon Telegraph and Telephone Corporation
+
+CONTAINER_IMG_NAME=$1
+CMD=$2
+APP_DIR=`dirname ${0}`
+ENVSH=${APP_DIR}/ubuntu/dpdk/env.sh
+
+# Include env.sh
+if [ -e ${ENVSH} ];then
+  . ${ENVSH}
+else
+  _build_env='./build/main.py --only-envsh'
+  echo "[Error] ${ENVSH} does not exist!"
+  echo "You have to build image or run '${_build_env}' to create it."
+  exit
+fi
+
+if [ ! $2 ]; then
+  echo "usage: $0 [IMAGE] [COMMAND]"
+  exit
+fi
+
+#cd ${APP_DIR}; \
+sudo docker run -i -t \
+	-e http_proxy=${http_proxy} \
+	-e https_proxy=${https_proxy} \
+	-e HTTP_PROXY=${http_proxy} \
+	-e HTTPS_PROXY=${https_proxy} \
+	-e RTE_SDK=${RTE_SDK} \
+	-e RTE_TARGET=${RTE_TARGET} \
+	${CONTAINER_IMG_NAME} \
+  ${CMD}
-- 
2.17.1

  parent reply	other threads:[~2018-06-15  8:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  8:37 [spp] [PATCH 00/15] Add SPP container tools ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 01/15] tools/sppc: add SPP container build tool ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 02/15] tools/sppc: add dockerfiles for DPDK ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 03/15] tools/sppc: add dockerfiles for pktgen ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 04/15] tools/sppc: add dockerfiles for SPP ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 05/15] tools/sppc: add spp-primary app continer ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 06/15] tools/sppc: add spp-nfv " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 07/15] tools/sppc: add spp-vm " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 08/15] tools/sppc: add l2fwd " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 09/15] tools/sppc: add testpmd " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 10/15] tools/sppc: add l3fwd " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 11/15] tools/sppc: add pktgen " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 12/15] tools/sppc: add load-balancer " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 13/15] tools/sppc: add helloworld " ogawa.yasufumi
2018-06-15  8:37 ` ogawa.yasufumi [this message]
2018-06-15  8:37 ` [spp] [PATCH 15/15] tools/sppc: add spp launcher script ogawa.yasufumi
2018-08-15 15:34 ` [spp] [PATCH 00/15] Add SPP container tools Ferruh Yigit

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=20180615083754.20220-15-ogawa.yasufumi@lab.ntt.co.jp \
    --to=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=spp@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).