From: "Xu, HuilongX" <huilongx.xu@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mk:fix second compile error
Date: Fri, 19 Aug 2016 03:04:02 +0000 [thread overview]
Message-ID: <DF2A19295B96364286FEB7F3DDA27A4637B92785@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20160809082713.GA72228@bricha3-MOBL3>
Hi Brue,
Thanks a lot for your comments. I will send V2 patch.
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Tuesday, August 09, 2016 4:27 PM
> To: Xu, HuilongX
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] mk:fix second compile error
>
> On Tue, Aug 09, 2016 at 02:01:58PM +0800, xu,huilong wrote:
> > when compile different targets on a same environment.
> > The second compile will failed, because test_resource obj file
> > can't auto clearn by makfile.
> >
> > Signed-off-by: xu,huilong <huilongx.xu@intel.com>
> > ---
> > mk/rte.app.mk | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/mk/rte.app.mk b/mk/rte.app.mk
> > index eb28e11..d23e8b9 100644
> > --- a/mk/rte.app.mk
> > +++ b/mk/rte.app.mk
> > @@ -263,7 +263,8 @@ $(RTE_OUTPUT)/app/$(APP).map: $(APP)
> > #
> > .PHONY: clean
> > clean: _postclean
> > - $(Q)rm -f $(_BUILD_TARGETS) $(_INSTALL_TARGETS) $(_CLEAN_TARGETS)
> > + $(Q)rm -f $(_BUILD_TARGETS) $(_INSTALL_TARGETS) $(_CLEAN_TARGETS)
> \
> > + test_resource.res test_resource_c.o test_resource_c.res.o
> >
> This fix looks very specific to the test application, and specific files
> in
> that application. Can it be made more generic so that it will work if we
> add
> other resource files to the test app without us having to modify the
> top-level
> application makefile.
>
> Regards,
> /Bruce
next prev parent reply other threads:[~2016-08-19 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 6:01 xu,huilong
2016-08-09 8:27 ` Bruce Richardson
2016-08-19 3:04 ` Xu, HuilongX [this message]
2016-08-11 1:38 ` Xu, HuilongX
2016-08-22 13:55 ` 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=DF2A19295B96364286FEB7F3DDA27A4637B92785@SHSMSX101.ccr.corp.intel.com \
--to=huilongx.xu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).