From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "Gao, Liming" <gaoliming@byosoft.com.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: 'Rebecca Cran' <rebecca@bsdio.com>,
"Feng, Bob C" <bob.c.feng@intel.com>,
"Chen, Christine" <yuwei.chen@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [Patch 1/1] BaseTools/Conf: Add quotes to ADDDEBUGFLAG in tools_def.txt
Date: Sat, 6 May 2023 04:55:17 +0000 [thread overview]
Message-ID: <CO1PR11MB4929E5F287CE87B9E858BD01D2739@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <024501d97fc7$02d010f0$087032d0$@byosoft.com.cn>
The issue I saw was a mix of / and \ in the file path. On Windows $(DEBUG_DIR) would
Have '\' in path and then a '/' before $(MODULE_NAME). Without the quotes, this
would generate an error. With quotes, it would get the full filename correct.
On Linux, only '/' are used for the whole path and everything works with and
Without quotes.
Mike
> -----Original Message-----
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Friday, May 5, 2023 8:01 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: 'Rebecca Cran' <rebecca@bsdio.com>; Feng, Bob C
> <bob.c.feng@intel.com>; Chen, Christine <yuwei.chen@intel.com>
> Subject: 回复: [edk2-devel] [Patch 1/1] BaseTools/Conf: Add quotes to
> ADDDEBUGFLAG in tools_def.txt
>
> Mike:
> Do you mean $(DEBUG_DIR)/$(MODULE_NAME).debug file path may have
> space on
> windows OS? Does the workspace directory include the space?
>
> Thanks
> Liming
> > -----邮件原件-----
> > 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Michael D
> > Kinney
> > 发送时间: 2023年5月6日 10:47
> > 收件人: devel@edk2.groups.io
> > 抄送: Rebecca Cran <rebecca@bsdio.com>; Liming Gao
> > <gaoliming@byosoft.com.cn>; Bob Feng <bob.c.feng@intel.com>; Yuwei
> Chen
> > <yuwei.chen@intel.com>
> > 主题: [edk2-devel] [Patch 1/1] BaseTools/Conf: Add quotes to
> > ADDDEBUGFLAG in tools_def.txt
> >
> > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4448
> >
> > Update tools_def.txt to add quotes around the file target in
> > OBJCOPY_ADDDEBUGFLAGS for compatibility with GCC like tool
> > chains used on Windows.
> >
> > Cc: Rebecca Cran <rebecca@bsdio.com>
> > Cc: Liming Gao <gaoliming@byosoft.com.cn>
> > Cc: Bob Feng <bob.c.feng@intel.com>
> > Cc: Yuwei Chen <yuwei.chen@intel.com>
> > Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
> > ---
> > BaseTools/Conf/tools_def.template | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/BaseTools/Conf/tools_def.template
> > b/BaseTools/Conf/tools_def.template
> > index 1b3a9e7a540a..535dda1d5d99 100755
> > --- a/BaseTools/Conf/tools_def.template
> > +++ b/BaseTools/Conf/tools_def.template
> > @@ -731,9 +731,9 @@ NOOPT_VS2019_AARCH64_DLINK_FLAGS =
> > /NOLOGO /NODEFAULTLIB /IGNORE:4001 /OPT:REF
> > *_*_*_OBJCOPY_FLAGS = objcopy not needed for
> > *_*_*_SYMRENAME_PATH = echo
> > *_*_*_SYMRENAME_FLAGS = Symbol renaming not needed for
> > -DEBUG_*_*_OBJCOPY_ADDDEBUGFLAG =
> > --add-gnu-debuglink=$(DEBUG_DIR)/$(MODULE_NAME).debug
> > +DEBUG_*_*_OBJCOPY_ADDDEBUGFLAG =
> > --add-gnu-debuglink="$(DEBUG_DIR)/$(MODULE_NAME).debug"
> > RELEASE_*_*_OBJCOPY_ADDDEBUGFLAG =
> > -NOOPT_*_*_OBJCOPY_ADDDEBUGFLAG =
> > --add-gnu-debuglink=$(DEBUG_DIR)/$(MODULE_NAME).debug
> > +NOOPT_*_*_OBJCOPY_ADDDEBUGFLAG =
> > --add-gnu-debuglink="$(DEBUG_DIR)/$(MODULE_NAME).debug"
> > *_*_*_OBJCOPY_STRIPFLAG = --strip-unneeded -R .eh_frame
> > *_*_*_DTC_FLAGS = -H epapr
> > *_*_*_DTCPP_PATH = DEF(DTCPP_BIN)
> > --
> > 2.40.1.windows.1
> >
> >
> >
> >
> >
>
>
next prev parent reply other threads:[~2023-05-06 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 2:46 [Patch 1/1] BaseTools/Conf: Add quotes to ADDDEBUGFLAG in tools_def.txt Michael D Kinney
2023-05-06 3:01 ` 回复: [edk2-devel] " gaoliming
2023-05-06 4:55 ` Michael D Kinney [this message]
2023-05-06 5:39 ` gaoliming
2023-05-06 16:28 ` Michael D Kinney
2023-05-06 9:40 ` Rebecca Cran
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-list 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=CO1PR11MB4929E5F287CE87B9E858BD01D2739@CO1PR11MB4929.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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