From: yepings@qti.qualcomm.com
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"michael.d.kinney@intel.com" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] BaseTools: how to generate PcdValueInit without VS?
Date: Tue, 30 May 2023 08:38:30 +0000 [thread overview]
Message-ID: <CH0PR02MB79009388541B4A1BBD49A54C8D4B9@CH0PR02MB7900.namprd02.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB492958E15F297FAB512E6630D2419@CO1PR11MB4929.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Hi Mike,
Thanks for your comments.
According to DscBuildData.py , it only supports VS on windows OS. How can we support Cygwin to compile Pcdvalueinit on windows OS?
Thanks
Yepings
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Michael D Kinney
Sent: Thursday, May 25, 2023 12:10 AM
To: devel@edk2.groups.io; Yeping Song <yepings@qti.qualcomm.com>
Cc: Kinney, Michael D <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] BaseTools: how to generate PcdValueInit without VS?
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
It is supposed to use the host compiler. Same one used to build BaseTools/Source/C
Mike
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of yepings@qti.qualcomm.com<mailto:yepings@qti.qualcomm.com>
Sent: Wednesday, May 24, 2023 1:58 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [edk2-devel] BaseTools: how to generate PcdValueInit without VS?
Hi maintainers,
PcdValueInit compilation requests VS on windows OS. Is there any other way to generate PcdValueInit without VS?
Thanks
Yepings.
[-- Attachment #2: Type: text/html, Size: 4627 bytes --]
next prev parent reply other threads:[~2023-05-30 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 8:58 BaseTools: how to generate PcdValueInit without VS? yepings
2023-05-24 16:10 ` [edk2-devel] " Michael D Kinney
2023-05-30 8:38 ` yepings [this message]
2023-05-30 15:32 ` Michael D Kinney
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=CH0PR02MB79009388541B4A1BBD49A54C8D4B9@CH0PR02MB7900.namprd02.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