From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1] framwork: align directory changes in dpdk
Date: Fri, 1 Mar 2019 05:40:27 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA38099@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1551349351-56721-1-git-send-email-wenjiex.a.li@intel.com>
According to dpdk commit: a9de470, the autotests app was removed to the "app" folder, and there is no separate build task necessary for building the autotests using "make test-build" while "make" covering the autotests build.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Thursday, February 28, 2019 6:23 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1] framwork: align directory changes in dpdk
>
> DPDK directories changed as below:
> 1 move test/test/ to app/test/
> 2 move test/test-acl/ to app/test-acl/
> 3 move test/test-pipeline/ to app/test-pipeline/
> 4 move test/test-cmdline/ to app/test-cmdline/
>
> Align the changes in dts.
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> framework/project_dpdk.py | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/framework/project_dpdk.py b/framework/project_dpdk.py index
> 2ad01e8..38d99f4 100644
> --- a/framework/project_dpdk.py
> +++ b/framework/project_dpdk.py
> @@ -259,12 +259,14 @@ class DPDKdut(Dut):
> assert ("No rule to make" not in out), "No rule to make error..."
>
> def build_install_dpdk_test_app(self, target, build_time, os_type="linux"):
> - cmd_build_test = "make -j %d -C test/" % (self.number_of_cores)
> - if os_type == "freebsd":
> - cmd_build_test = "make -j %d -C test/ CC=gcc48" %
> (self.number_of_cores)
> -
> - self.send_expect(cmd_build_test, "# ", build_time)
> - app_list = ['./test/test/test', './test/test-acl/testacl', './test/test-
> pipeline/testpipeline', './test/cmdline_test/cmdline_test']
> + app_dir_list = ['app/test/', 'app/test-acl/', 'app/test-pipeline/', 'app/test-
> cmdline/']
> + for app_dir in app_dir_list:
> + cmd_build_test = "make -j %d -C %s" % (self.number_of_cores, app_dir)
> + if os_type == "freebsd":
> + cmd_build_test = "make -j %d -C %s CC=gcc48" %
> (self.number_of_cores, app_dir)
> + self.send_expect(cmd_build_test, "# ", build_time)
> +
> + app_list = ['app/test/test', 'app/test-acl/testacl',
> + 'app/test-pipeline/testpipeline', 'app/test-cmdline/cmdline_test']
> for app in app_list:
> self.send_expect('cp -f %s ./%s/app' % (app, target), "# ", 30)
>
> --
> 2.17.2
prev parent reply other threads:[~2019-03-01 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 10:22 Wenjie Li
2019-03-01 1:51 ` Zhu, ShuaiX
2019-03-01 5:40 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BA38099@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wenjiex.a.li@intel.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).