From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Satish Rangarajan <satishr@chelsio.com>,
Indranil Choudhury <indranil@chelsio.com>
Subject: Re: [PATCH 1/4] net/cxgbe: use relative paths for including header files
Date: Wed, 19 Dec 2018 18:12:03 +0530 [thread overview]
Message-ID: <20181219124202.GC11932@chelsio.com> (raw)
In-Reply-To: <80fd308b-07a4-056b-60be-5fcd9143d6f4@intel.com>
On Tuesday, December 12/18/18, 2018 at 23:53:38 +0530, Ferruh Yigit wrote:
> On 12/13/2018 3:02 PM, Rahul Lakkireddy wrote:
> > Explicitly state header file location using relative paths.
> >
> > Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> > ---
> > drivers/net/cxgbe/Makefile | 2 --
> > drivers/net/cxgbe/base/adapter.h | 4 ++--
> > drivers/net/cxgbe/base/common.h | 2 +-
> > drivers/net/cxgbe/clip_tbl.c | 2 +-
> > drivers/net/cxgbe/cxgbe.h | 4 ++--
> > drivers/net/cxgbe/cxgbe_ethdev.c | 2 +-
> > drivers/net/cxgbe/cxgbe_filter.c | 7 ++++---
> > drivers/net/cxgbe/cxgbe_filter.h | 2 +-
> > drivers/net/cxgbe/cxgbe_flow.c | 2 +-
> > drivers/net/cxgbe/cxgbe_main.c | 6 +++---
> > drivers/net/cxgbe/cxgbevf_ethdev.c | 2 +-
> > drivers/net/cxgbe/cxgbevf_main.c | 6 +++---
> > drivers/net/cxgbe/l2t.c | 3 ++-
> > drivers/net/cxgbe/l2t.h | 2 +-
> > drivers/net/cxgbe/mps_tcam.h | 2 +-
> > drivers/net/cxgbe/sge.c | 6 +++---
> > 16 files changed, 27 insertions(+), 27 deletions(-)
> >
> > diff --git a/drivers/net/cxgbe/Makefile b/drivers/net/cxgbe/Makefile
> > index 68466f13e..d809f4720 100644
> > --- a/drivers/net/cxgbe/Makefile
> > +++ b/drivers/net/cxgbe/Makefile
> > @@ -9,8 +9,6 @@ include $(RTE_SDK)/mk/rte.vars.mk
> > #
> > LIB = librte_pmd_cxgbe.a
> >
> > -CFLAGS += -I$(SRCDIR)/base/
> > -CFLAGS += -I$(SRCDIR)
> > CFLAGS += -O3
> > CFLAGS += $(WERROR_FLAGS)
>
> Hi Rahul,
>
> What issue do you observe if you don't use relative paths?
The Intel C++ compiler [1] is not able to locate the header files without
relative path in Windows. We get the following error for these header
files.
# base\common.h(9): error : cannot open source file "cxgbe_compat.h"
#include "cxgbe_compat.h"
^
We could reproduce the same error by removing the above two lines for
Linux. To keep it consistent across both OS, I'm using relative paths
for both.
[1] https://software.intel.com/en-us/parallel-studio-xe
Thanks,
Rahul
next prev parent reply other threads:[~2018-12-19 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 15:02 [PATCH 0/4] net/cxgbe: fix build for Microsoft Windows OS support Rahul Lakkireddy
2018-12-13 15:02 ` [PATCH 1/4] net/cxgbe: use relative paths for including header files Rahul Lakkireddy
2018-12-18 18:23 ` Ferruh Yigit
2018-12-19 12:42 ` Rahul Lakkireddy [this message]
2018-12-13 15:02 ` [PATCH 2/4] net/cxgbe: fix macros related to logs for Windows Rahul Lakkireddy
2018-12-18 18:25 ` Ferruh Yigit
2018-12-19 12:39 ` Rahul Lakkireddy
2018-12-19 13:45 ` Ferruh Yigit
2018-12-19 14:11 ` Rahul Lakkireddy
2018-12-13 15:02 ` [PATCH 3/4] net/cxgbe: only redefine symbols when not available " Rahul Lakkireddy
2018-12-18 18:26 ` Ferruh Yigit
2018-12-19 12:41 ` Rahul Lakkireddy
2018-12-13 15:02 ` [PATCH 4/4] net/cxgbe: fix other misc build issues " Rahul Lakkireddy
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=20181219124202.GC11932@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=indranil@chelsio.com \
--cc=satishr@chelsio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.