[edk2] edk2 build problems

Discussion:

Tony

2015-07-09 05:25:36 UTC

I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.
My current environment is:win 7 pro 64bitvs studio express 2013 for desktopedk2
The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.
I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:
f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warningtreated as error - no 'object' file generatedf:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEfiGlobalVariable2' undefined; assuming extern returning intNMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\cl.exe"' : return code '0x2'Stop.

build... : error 7000: Failed to execute command C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /nologo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib]

buiLD... : error F002: Failed to build module f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86, DEBUG]
- Failed -Build end time: 14:44:21, Jul.09 2015Build total time: 00:00:09
I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.
Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.
I will appreciate your assistance.
Thanks,Tony

Neeraj Ladkani

2015-07-09 05:35:58 UTC

Permalink

âIf you want to build Shell, please update your target_conf as

ACTIVE_PLATFORM = ShellPkg\ShellPkg.dsc

On Wed, Jul 8, 2015 at 10:25 PM, Tony <***@hotmail.com> wrote:

> I am very new to uefi dev and trying to understand how the environment
> needs to be setup to bring up the uefi shell.
>
> My current environment is:
> win 7 pro 64bit
> vs studio express 2013 for desktop
> edk2
>
> The edk2 binaries are in the f:\ folder. I have modified target_arch &
> toolchain to reflect my build platforms. That said I have tried x64 as my
> target_arch too.
>
> I like to think that I have set up the environment correctly (after
> ironing other errors) but when I do a build from vs2013 command line (and
> also from x64 command line) I get the following error for which I cannot
> seem to find a resolution:
>
> *f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220:
> warning*
> *treated as error - no 'object' file generated*
> *f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013:
> 'GetEf*
> *iGlobalVariable2' undefined; assuming extern returning int*
> *NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio 12.0*
> *\Vc\bin\cl.exe"' : return code '0x2'*
> *Stop.*
>
>
> *build...*
> * : error 7000: Failed to execute command*
> * C:\Program Files (x86)\Microsoft Visual Studio
> 12.0\Vc\bin\nmake.exe /no*
> *logo tbuild
> [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\U*
> *efiHiiLib\UefiHiiLib]*
>
>
> *buiLD...*
> * : error F002: Failed to build module*
> * f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32,
> VS2013x86,*
> * DEBUG]*
>
> *- Failed -*
> *Build end time: 14:44:21, Jul.09 2015*
> *Build total time: 00:00:09*
>
> I read somewhere that the winsdk needs to change from the default v6.0a to
> one that suits your vs studio. I changed that to v8.0a to no effect.
>
> Following the guide from edk2 I set my active_platform to be
> MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I
> have tried that as well. What is the difference and why must we chose one
> over the other.
>
> I will appreciate your assistance.
>
> Thanks,
> Tony
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> edk2-devel mailing list
> edk2-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>

--
Thanks
Neeraj

Andrew Fish

2015-07-09 05:37:47 UTC

Permalink

This post might be inappropriate. Click to display it.

Thomas Rognon

2015-07-09 06:29:42 UTC

Permalink

The UEFI shell is an application that can be run in a UEFI environment
(either on real or emulated hardware) similar to how the Windows command
prompt runs in the Windows OS. So first you need to have a UEFI
environment. There are many options here. There is a UEFI environment on
your computer before the Windows OS loads, so you can build and .efi file
from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB
and boot to it from your boot manager. You can also build an emulated
(Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.

The simplest route for you is probably to build Nt32Pkg. It creates the
emulated UEFI environment and also builds the shell application for you and
starts it by default. There used to be really simple instructions on
tianocore, but things have gotten moved around a lot. Pretty much you just
build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the
Build folder. You run the .exe and it brings up the emulated environment
and starts the shell application. If my memory is correct, you just need to
change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the
command line run "edksetup.bat --nt32" to set up your build environment,
then "build" to actually build Nt32Pkg, then "build run" to run the .exe
that is produced.

Btw, MdeModulePkg is just a collection of drivers and libraries, it is not
a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf)
pull things together into a complete firmware. For real hardware, people
create their own packages (not included in edk2, of course) that pull
things together with platform specific code.

On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com> wrote:

> I am very new to uefi dev and trying to understand how the environment
> needs to be setup to bring up the uefi shell.
>
> My current environment is:
> win 7 pro 64bit
> vs studio express 2013 for desktop
> edk2
>
> The edk2 binaries are in the f:\ folder. I have modified target_arch &
> toolchain to reflect my build platforms. That said I have tried x64 as my
> target_arch too.
>
> I like to think that I have set up the environment correctly (after
> ironing other errors) but when I do a build from vs2013 command line (and
> also from x64 command line) I get the following error for which I cannot
> seem to find a resolution:
>
> *f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220:
> warning*
> *treated as error - no 'object' file generated*
> *f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013:
> 'GetEf*
> *iGlobalVariable2' undefined; assuming extern returning int*
> *NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio 12.0*
> *\Vc\bin\cl.exe"' : return code '0x2'*
> *Stop.*
>
>
> *build...*
> * : error 7000: Failed to execute command*
> * C:\Program Files (x86)\Microsoft Visual Studio
> 12.0\Vc\bin\nmake.exe /no*
> *logo tbuild
> [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\U*
> *efiHiiLib\UefiHiiLib]*
>
>
> *buiLD...*
> * : error F002: Failed to build module*
> * f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32,
> VS2013x86,*
> * DEBUG]*
>
> *- Failed -*
> *Build end time: 14:44:21, Jul.09 2015*
> *Build total time: 00:00:09*
>
> I read somewhere that the winsdk needs to change from the default v6.0a to
> one that suits your vs studio. I changed that to v8.0a to no effect.
>
> Following the guide from edk2 I set my active_platform to be
> MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I
> have tried that as well. What is the difference and why must we chose one
> over the other.
>
> I will appreciate your assistance.
>
> Thanks,
> Tony
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> edk2-devel mailing list
> edk2-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>

Tony

2015-07-10 00:13:38 UTC

Permalink

Hello Thomas,
Many thanks for your advise. I have changed my active_platform to Nt32Pkg/Nt32Pkg.dsc but I still get the exact same error as before.

I used the 32bit command prompt from vs studio 2013.
Thanks.
Date: Thu, 9 Jul 2015 01:29:42 -0500
From: ***@gmail.com
To: edk2-***@lists.sourceforge.net
Subject: Re: [edk2] edk2 build problems

The UEFI shell is an application that can be run in a UEFI environment (either on real or emulated hardware) similar to how the Windows command prompt runs in the Windows OS. So first you need to have a UEFI environment. There are many options here. There is a UEFI environment on your computer before the Windows OS loads, so you can build and .efi file from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB and boot to it from your boot manager. You can also build an emulated (Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.
The simplest route for you is probably to build Nt32Pkg. It creates the emulated UEFI environment and also builds the shell application for you and starts it by default. There used to be really simple instructions on tianocore, but things have gotten moved around a lot. Pretty much you just build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the Build folder. You run the .exe and it brings up the emulated environment and starts the shell application. If my memory is correct, you just need to change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the command line run "edksetup.bat --nt32" to set up your build environment, then "build" to actually build Nt32Pkg, then "build run" to run the .exe that is produced.
Btw, MdeModulePkg is just a collection of drivers and libraries, it is not a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf) pull things together into a complete firmware. For real hardware, people create their own packages (not included in edk2, of course) that pull things together with platform specific code.
On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com> wrote:

I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.
My current environment is:win 7 pro 64bitvs studio express 2013 for desktopedk2
The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.
I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:
f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warningtreated as error - no 'object' file generatedf:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEfiGlobalVariable2' undefined; assuming extern returning intNMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\cl.exe"' : return code '0x2'Stop.

build... : error 7000: Failed to execute command C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /nologo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib]

buiLD... : error F002: Failed to build module f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86, DEBUG]
- Failed -Build end time: 14:44:21, Jul.09 2015Build total time: 00:00:09
I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.
Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.
I will appreciate your assistance.
Thanks,Tony

------------------------------------------------------------------------------

Don't Limit Your Business. Reach for the Cloud.

GigeNET's Cloud Solutions provide you with the tools and support that

you need to offload your IT needs and focus on growing your business.

Configured For All Businesses. Start Your Cloud Today.

https://www.gigenetcloud.com/
_______________________________________________

edk2-devel mailing list

edk2-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/edk2-devel

Tony

2015-07-10 00:22:00 UTC

Permalink

Hi Andrew, thanks for your reply. Could you please advise how I can check the versions of MdePkg & MdeModulePkg.
Thanks.

From: ***@hotmail.com
To: edk2-***@lists.sourceforge.net
Date: Fri, 10 Jul 2015 00:13:38 +0000
Subject: Re: [edk2] edk2 build problems

Hello Thomas,
Many thanks for your advise. I have changed my active_platform to Nt32Pkg/Nt32Pkg.dsc but I still get the exact same error as before.

I used the 32bit command prompt from vs studio 2013.
Thanks.
Date: Thu, 9 Jul 2015 01:29:42 -0500
From: ***@gmail.com
To: edk2-***@lists.sourceforge.net
Subject: Re: [edk2] edk2 build problems

The UEFI shell is an application that can be run in a UEFI environment (either on real or emulated hardware) similar to how the Windows command prompt runs in the Windows OS. So first you need to have a UEFI environment. There are many options here. There is a UEFI environment on your computer before the Windows OS loads, so you can build and .efi file from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB and boot to it from your boot manager. You can also build an emulated (Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.
The simplest route for you is probably to build Nt32Pkg. It creates the emulated UEFI environment and also builds the shell application for you and starts it by default. There used to be really simple instructions on tianocore, but things have gotten moved around a lot. Pretty much you just build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the Build folder. You run the .exe and it brings up the emulated environment and starts the shell application. If my memory is correct, you just need to change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the command line run "edksetup.bat --nt32" to set up your build environment, then "build" to actually build Nt32Pkg, then "build run" to run the .exe that is produced.
Btw, MdeModulePkg is just a collection of drivers and libraries, it is not a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf) pull things together into a complete firmware. For real hardware, people create their own packages (not included in edk2, of course) that pull things together with platform specific code.
On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com> wrote:

I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.
My current environment is:win 7 pro 64bitvs studio express 2013 for desktopedk2
The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.
I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:
f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warningtreated as error - no 'object' file generatedf:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEfiGlobalVariable2' undefined; assuming extern returning intNMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\cl.exe"' : return code '0x2'Stop.

build... : error 7000: Failed to execute command C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /nologo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib]

buiLD... : error F002: Failed to build module f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86, DEBUG]
- Failed -Build end time: 14:44:21, Jul.09 2015Build total time: 00:00:09
I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.
Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.
I will appreciate your assistance.
Thanks,Tony

------------------------------------------------------------------------------

Don't Limit Your Business. Reach for the Cloud.

GigeNET's Cloud Solutions provide you with the tools and support that

you need to offload your IT needs and focus on growing your business.

Configured For All Businesses. Start Your Cloud Today.

https://www.gigenetcloud.com/
_______________________________________________

edk2-devel mailing list

edk2-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Tony

2015-07-10 00:27:52 UTC

Permalink

Hello Neeraj,
Thanks for your reply. I did as you suggested and updated my target_conf file to replace my active_platform withACTIVE_PLATFORM = ShellPkg\ShellPkg.dsc
I ran the build from x86 vs studio command line and got exactly the same error as before.
Thanks
From: ***@hotmail.com
To: edk2-***@lists.sourceforge.net
Subject: RE: [edk2] edk2 build problems
Date: Fri, 10 Jul 2015 00:22:00 +0000

Hi Andrew, thanks for your reply. Could you please advise how I can check the versions of MdePkg & MdeModulePkg.
Thanks.

From: ***@hotmail.com
To: edk2-***@lists.sourceforge.net
Date: Fri, 10 Jul 2015 00:13:38 +0000
Subject: Re: [edk2] edk2 build problems

Hello Thomas,
Many thanks for your advise. I have changed my active_platform to Nt32Pkg/Nt32Pkg.dsc but I still get the exact same error as before.

I used the 32bit command prompt from vs studio 2013.
Thanks.
Date: Thu, 9 Jul 2015 01:29:42 -0500
From: ***@gmail.com
To: edk2-***@lists.sourceforge.net
Subject: Re: [edk2] edk2 build problems

The UEFI shell is an application that can be run in a UEFI environment (either on real or emulated hardware) similar to how the Windows command prompt runs in the Windows OS. So first you need to have a UEFI environment. There are many options here. There is a UEFI environment on your computer before the Windows OS loads, so you can build and .efi file from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB and boot to it from your boot manager. You can also build an emulated (Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.
The simplest route for you is probably to build Nt32Pkg. It creates the emulated UEFI environment and also builds the shell application for you and starts it by default. There used to be really simple instructions on tianocore, but things have gotten moved around a lot. Pretty much you just build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the Build folder. You run the .exe and it brings up the emulated environment and starts the shell application. If my memory is correct, you just need to change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the command line run "edksetup.bat --nt32" to set up your build environment, then "build" to actually build Nt32Pkg, then "build run" to run the .exe that is produced.
Btw, MdeModulePkg is just a collection of drivers and libraries, it is not a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf) pull things together into a complete firmware. For real hardware, people create their own packages (not included in edk2, of course) that pull things together with platform specific code.
On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com> wrote:

I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.
My current environment is:win 7 pro 64bitvs studio express 2013 for desktopedk2
The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.
I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:
f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warningtreated as error - no 'object' file generatedf:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEfiGlobalVariable2' undefined; assuming extern returning intNMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\cl.exe"' : return code '0x2'Stop.

build... : error 7000: Failed to execute command C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /nologo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib]

buiLD... : error F002: Failed to build module f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86, DEBUG]
- Failed -Build end time: 14:44:21, Jul.09 2015Build total time: 00:00:09
I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.
Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.
I will appreciate your assistance.
Thanks,Tony

------------------------------------------------------------------------------

Don't Limit Your Business. Reach for the Cloud.

GigeNET's Cloud Solutions provide you with the tools and support that

you need to offload your IT needs and focus on growing your business.

Configured For All Businesses. Start Your Cloud Today.

https://www.gigenetcloud.com/
_______________________________________________

edk2-devel mailing list

edk2-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Tony

2015-07-10 00:31:37 UTC

Permalink

I got it from http://sourceforge.net/projects/edk2/files/EDK%20II%20Releases/Demo%20apps/EDKII_Training_July2012.zip/download

From: ***@hotmail.com
To: edk2-***@lists.sourceforge.net
Date: Fri, 10 Jul 2015 00:27:52 +0000
Subject: Re: [edk2] edk2 build problems

Hello Neeraj,
Thanks for your reply. I did as you suggested and updated my target_conf file to replace my active_platform withACTIVE_PLATFORM = ShellPkg\ShellPkg.dsc
I ran the build from x86 vs studio command line and got exactly the same error as before.
Thanks
From: ***@hotmail.com
To: edk2-***@lists.sourceforge.net
Subject: RE: [edk2] edk2 build problems
Date: Fri, 10 Jul 2015 00:22:00 +0000

Hi Andrew, thanks for your reply. Could you please advise how I can check the versions of MdePkg & MdeModulePkg.
Thanks.

From: ***@hotmail.com
To: edk2-***@lists.sourceforge.net
Date: Fri, 10 Jul 2015 00:13:38 +0000
Subject: Re: [edk2] edk2 build problems

Hello Thomas,
Many thanks for your advise. I have changed my active_platform to Nt32Pkg/Nt32Pkg.dsc but I still get the exact same error as before.

I used the 32bit command prompt from vs studio 2013.
Thanks.
Date: Thu, 9 Jul 2015 01:29:42 -0500
From: ***@gmail.com
To: edk2-***@lists.sourceforge.net
Subject: Re: [edk2] edk2 build problems

The UEFI shell is an application that can be run in a UEFI environment (either on real or emulated hardware) similar to how the Windows command prompt runs in the Windows OS. So first you need to have a UEFI environment. There are many options here. There is a UEFI environment on your computer before the Windows OS loads, so you can build and .efi file from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB and boot to it from your boot manager. You can also build an emulated (Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.
The simplest route for you is probably to build Nt32Pkg. It creates the emulated UEFI environment and also builds the shell application for you and starts it by default. There used to be really simple instructions on tianocore, but things have gotten moved around a lot. Pretty much you just build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the Build folder. You run the .exe and it brings up the emulated environment and starts the shell application. If my memory is correct, you just need to change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the command line run "edksetup.bat --nt32" to set up your build environment, then "build" to actually build Nt32Pkg, then "build run" to run the .exe that is produced.
Btw, MdeModulePkg is just a collection of drivers and libraries, it is not a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf) pull things together into a complete firmware. For real hardware, people create their own packages (not included in edk2, of course) that pull things together with platform specific code.
On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com> wrote:

I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.
My current environment is:win 7 pro 64bitvs studio express 2013 for desktopedk2
The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.
I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:
f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warningtreated as error - no 'object' file generatedf:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEfiGlobalVariable2' undefined; assuming extern returning intNMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\cl.exe"' : return code '0x2'Stop.

build... : error 7000: Failed to execute command C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /nologo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib]

buiLD... : error F002: Failed to build module f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86, DEBUG]
- Failed -Build end time: 14:44:21, Jul.09 2015Build total time: 00:00:09
I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.
Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.
I will appreciate your assistance.
Thanks,Tony

------------------------------------------------------------------------------

Don't Limit Your Business. Reach for the Cloud.

GigeNET's Cloud Solutions provide you with the tools and support that

you need to offload your IT needs and focus on growing your business.

Configured For All Businesses. Start Your Cloud Today.

https://www.gigenetcloud.com/
_______________________________________________

edk2-devel mailing list

edk2-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Andrew Fish

2015-07-10 01:17:38 UTC

Permalink

> On Jul 9, 2015, at 5:31 PM, Tony <***@hotmail.com> wrote:
>
> I got it from http://sourceforge.net/projects/edk2/files/EDK%20II%20Releases/Demo%20apps/EDKII_Training_July2012.zip/download <http://sourceforge.net/projects/edk2/files/EDK%20II%20Releases/Demo%20apps/EDKII_Training_July2012.zip/download>
>

The error message implies your MdeModulePkg is not the same as the ZIP.

The ZIP file MdeModulePkg\Library\UefiHiiLib\HiiString.c:253 matches the MdePkg library include file.
PlatformLanguage = GetEfiGlobalVariable (L"PlatformLang");

So you did something to break it?

Thanks,

Andrew Fish

> From: ***@hotmail.com <mailto:***@hotmail.com>
> To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
> Date: Fri, 10 Jul 2015 00:27:52 +0000
> Subject: Re: [edk2] edk2 build problems
>
> Hello Neeraj,
>
> Thanks for your reply. I did as you suggested and updated my target_conf file to replace my active_platform with
> ACTIVE_PLATFORM = ShellPkg\ShellPkg.dsc
>
> I ran the build from x86 vs studio command line and got exactly the same error as before.
>
> Thanks
>
> From: ***@hotmail.com <mailto:***@hotmail.com>
> To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
> Subject: RE: [edk2] edk2 build problems
> Date: Fri, 10 Jul 2015 00:22:00 +0000
>
> Hi Andrew, thanks for your reply. Could you please advise how I can check the versions of MdePkg & MdeModulePkg.
>
> Thanks.
>
> From: ***@hotmail.com <mailto:***@hotmail.com>
> To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
> Date: Fri, 10 Jul 2015 00:13:38 +0000
> Subject: Re: [edk2] edk2 build problems
>
> Hello Thomas,
>
> Many thanks for your advise. I have changed my active_platform to Nt32Pkg/Nt32Pkg.dsc but I still get the exact same error as before.
>
> I used the 32bit command prompt from vs studio 2013.
>
> Thanks.
> Date: Thu, 9 Jul 2015 01:29:42 -0500
> From: ***@gmail.com <mailto:***@gmail.com>
> To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
> Subject: Re: [edk2] edk2 build problems
>
> The UEFI shell is an application that can be run in a UEFI environment (either on real or emulated hardware) similar to how the Windows command prompt runs in the Windows OS. So first you need to have a UEFI environment. There are many options here. There is a UEFI environment on your computer before the Windows OS loads, so you can build and .efi file from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB and boot to it from your boot manager. You can also build an emulated (Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.
>
> The simplest route for you is probably to build Nt32Pkg. It creates the emulated UEFI environment and also builds the shell application for you and starts it by default. There used to be really simple instructions on tianocore, but things have gotten moved around a lot. Pretty much you just build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the Build folder. You run the .exe and it brings up the emulated environment and starts the shell application. If my memory is correct, you just need to change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the command line run "edksetup.bat --nt32" to set up your build environment, then "build" to actually build Nt32Pkg, then "build run" to run the .exe that is produced.
>
> Btw, MdeModulePkg is just a collection of drivers and libraries, it is not a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf) pull things together into a complete firmware. For real hardware, people create their own packages (not included in edk2, of course) that pull things together with platform specific code.
>
> On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com <mailto:***@hotmail.com>> wrote:
> I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.
>
> My current environment is:
> win 7 pro 64bit
> vs studio express 2013 for desktop
> edk2
>
> The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.
>
> I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:
>
> f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warning
> treated as error - no 'object' file generated
> f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEf
> iGlobalVariable2' undefined; assuming extern returning int
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
> \Vc\bin\cl.exe"' : return code '0x2'
> Stop.
>
>
> build...
> : error 7000: Failed to execute command
> C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /no
> logo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\U
> efiHiiLib\UefiHiiLib]
>
>
> buiLD...
> : error F002: Failed to build module
> f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86,
> DEBUG]
>
> - Failed -
> Build end time: 14:44:21, Jul.09 2015
> Build total time: 00:00:09
>
> I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.
>
> Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.
>
> I will appreciate your assistance.
>
> Thanks,
> Tony
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/ <https://www.gigenetcloud.com/>
> _______________________________________________
> edk2-devel mailing list
> edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/edk2-devel <https://lists.sourceforge.net/lists/listinfo/edk2-devel>
>
>
>
> ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ <https://www.gigenetcloud.com/>
> _______________________________________________ edk2-devel mailing list edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>https://lists.sourceforge.net/lists/listinfo/edk2-devel <https://lists.sourceforge.net/lists/listinfo/edk2-devel>
> ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ <https://www.gigenetcloud.com/>
> _______________________________________________ edk2-devel mailing list edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>https://lists.sourceforge.net/lists/listinfo/edk2-devel <https://lists.sourceforge.net/lists/listinfo/edk2-devel>
> ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ <https://www.gigenetcloud.com/>
> _______________________________________________ edk2-devel mailing list edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>https://lists.sourceforge.net/lists/listinfo/edk2-devel <https://lists.sourceforge.net/lists/listinfo/edk2-devel>------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/_______________________________________________ <https://www.gigenetcloud.com/_______________________________________________>
> edk2-devel mailing list
> edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/edk2-devel <https://lists.sourceforge.net/lists/listinfo/edk2-devel>

Scott Duplichan

2015-07-10 01:58:58 UTC

Permalink

Hello Tony,

That 3 year old snapshot doesn't support VS2013. See BaseTools/Conf/tools_def.template for a list of supported tool chains.

To build with VS2010 using Win64, do this:

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

d:\>"%VS100COMNTOOLS%\..\..\VC\vcvarsall.bat" x86

Setting environment for using Microsoft Visual Studio 2010 x86 tools.

d:\>cd D:\tmp\FW\edk2

D:\tmp\FW\edk2>edksetup.bat --nt32

D:\tmp\FW\edk2>build -p D:\tmp\FW\edk2\Nt32Pkg\Nt32Pkg.dsc -b DEBUG -t VS2010x86 -n 16 -a IA32

<snip>

FV Space Information

FVRECOVERY [79%Full] 2621440 total, 2078560 used, 542880 free

- Done -

Build end time: 20:47:03, Jul.09 2015

Build total time: 00:00:43

Thanks,

Scott

From: Tony [mailto:***@hotmail.com]
Sent: Thursday, July 09, 2015 07:32 PM
To: edk2-***@lists.sourceforge.net
Subject: Re: [edk2] edk2 build problems

I got it from http://sourceforge.net/projects/edk2/files/EDK%20II%20Releases/Demo%20apps/EDKII_Training_July2012.zip/download

_____

From: ***@hotmail.com <mailto:***@hotmail.com>
To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
Date: Fri, 10 Jul 2015 00:27:52 +0000
Subject: Re: [edk2] edk2 build problems

Hello Neeraj,

Thanks for your reply. I did as you suggested and updated my target_conf file to replace my active_platform with

ACTIVE_PLATFORM = ShellPkg\ShellPkg.dsc

I ran the build from x86 vs studio command line and got exactly the same error as before.

Thanks

_____

From: ***@hotmail.com <mailto:***@hotmail.com>
To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
Subject: RE: [edk2] edk2 build problems
Date: Fri, 10 Jul 2015 00:22:00 +0000

Hi Andrew, thanks for your reply. Could you please advise how I can check the versions of MdePkg & MdeModulePkg.

Thanks.

_____

From: ***@hotmail.com <mailto:***@hotmail.com>
To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
Date: Fri, 10 Jul 2015 00:13:38 +0000
Subject: Re: [edk2] edk2 build problems

Hello Thomas,

Many thanks for your advise. I have changed my active_platform to Nt32Pkg/Nt32Pkg.dsc but I still get the exact same error as before.

I used the 32bit command prompt from vs studio 2013.

Thanks.

_____

Date: Thu, 9 Jul 2015 01:29:42 -0500
From: ***@gmail.com <mailto:***@gmail.com>
To: edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
Subject: Re: [edk2] edk2 build problems

The UEFI shell is an application that can be run in a UEFI environment (either on real or emulated hardware) similar to how the Windows command prompt runs in the Windows OS. So first you need to have a UEFI environment. There are many options here. There is a UEFI environment on your computer before the Windows OS loads, so you can build and .efi file from ShellPkg or get the pre-built one from ShellBinPkg and put it on a USB and boot to it from your boot manager. You can also build an emulated (Nt32Pkg) or virtual (OVMF) UEFI environment from edk2.

The simplest route for you is probably to build Nt32Pkg. It creates the emulated UEFI environment and also builds the shell application for you and starts it by default. There used to be really simple instructions on tianocore, but things have gotten moved around a lot. Pretty much you just build Nt32Pkg (32-bit, of course) and it produces and .exe deep in the Build folder. You run the .exe and it brings up the emulated environment and starts the shell application. If my memory is correct, you just need to change your TOOL_CHAIN_TAG to VS2013x86, and in edk2 folder from the command line run "edksetup.bat --nt32" to set up your build environment, then "build" to actually build Nt32Pkg, then "build run" to run the .exe that is produced.

Btw, MdeModulePkg is just a collection of drivers and libraries, it is not a full firmware. Packages like OvmfPkg and Nt32Pkg (ones containing a .fdf) pull things together into a complete firmware. For real hardware, people create their own packages (not included in edk2, of course) that pull things together with platform specific code.

On Thu, Jul 9, 2015 at 12:25 AM, Tony <***@hotmail.com <mailto:***@hotmail.com> > wrote:

I am very new to uefi dev and trying to understand how the environment needs to be setup to bring up the uefi shell.

My current environment is:

win 7 pro 64bit

vs studio express 2013 for desktop

edk2

The edk2 binaries are in the f:\ folder. I have modified target_arch & toolchain to reflect my build platforms. That said I have tried x64 as my target_arch too.

I like to think that I have set up the environment correctly (after ironing other errors) but when I do a build from vs2013 command line (and also from x64 command line) I get the following error for which I cannot seem to find a resolution:

f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : error C2220: warning

treated as error - no 'object' file generated

f:\edk2\MdeModulePkg\Library\UefiHiiLib\HiiString.c(253) : warning C4013: 'GetEf

iGlobalVariable2' undefined; assuming extern returning int

NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0

\Vc\bin\cl.exe"' : return code '0x2'

Stop.

build...

: error 7000: Failed to execute command

C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /no

logo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\IA32\MdeModulePkg\Library\U

efiHiiLib\UefiHiiLib]

buiLD...

: error F002: Failed to build module

f:\edk2\MdeModulePkg\Library\UefiHiiLib\UefiHiiLib.inf [IA32, VS2013x86,

DEBUG]

- Failed -

Build end time: 14:44:21, Jul.09 2015

Build total time: 00:00:09

I read somewhere that the winsdk needs to change from the default v6.0a to one that suits your vs studio. I changed that to v8.0a to no effect.

Following the guide from edk2 I set my active_platform to be MdeModulePkg/MdeModulePkg.dsc. I have seen other people using Nt32Pkg. I have tried that as well. What is the difference and why must we chose one over the other.

I will appreciate your assistance.

Thanks,

Tony

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/
_______________________________________________ edk2-devel mailing list edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/
_______________________________________________ edk2-devel mailing list edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/
_______________________________________________ edk2-devel mailing list edk2-***@lists.sourceforge.net <mailto:edk2-***@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/edk2-devel

Tony

2015-07-16 05:48:52 UTC

Permalink

Hi there, I get the error below when trying to build a simple hello word program.
my environmet:

win 7 pro x64
vstudio 2013 express
tortoisesvn latest version
edk2 is saved to f:\

Following the directions here...http://tianocore.sourceforge.net/wiki/Windows_systems

I get these errors...

f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1583) : error
C2220: warning treated as error - no 'object' file generated
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1583) : warni
ng C4244: '=' : conversion from 'UINTN' to 'UINT16', possible loss of data
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1590) : warni
ng C4244: '=' : conversion from 'UINTN' to 'UINT16', possible loss of data
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1594) : warni
ng C4244: '=' : conversion from 'UINTN' to 'UINT16', possible loss of data
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
\Vc\bin\x86_amd64\cl.exe"' : return code '0x2'
Stop.

build...
: error 7000: Failed to execute command
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /no
logo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\X64\MdeModulePkg\Universal\
Console\TerminalDxe\TerminalDxe]

build...
: error F002: Failed to build module
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalDxe.inf [X64,
VS2013x86, DEBUG]

- Failed -
Build end time: 13:42:27, Jul.16 2015
Build total time: 00:01:22

f:\edk2>

Appreciate your help

Thanks,
Tony

Ni, Ruiyu

2015-07-16 05:59:41 UTC

Permalink

Can you update to latest version? The check-in attached fixed the issue.

From: Tony [mailto:***@hotmail.com]
Sent: Thursday, July 16, 2015 1:49 PM
To: edk2-***@lists.sourceforge.net
Subject: [edk2] FW: edk2 build problems

________________________________
Hi there, I get the error below when trying to build a simple hello word program.
my environmet:

win 7 pro x64
vstudio 2013 express
tortoisesvn latest version
edk2 is saved to f:\

Following the directions here...http://tianocore.sourceforge.net/wiki/Windows_systems

I get these errors...

f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1583) : error
C2220: warning treated as error - no 'object' file generated
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1583) : warni
ng C4244: '=' : conversion from 'UINTN' to 'UINT16', possible loss of data
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1590) : warni
ng C4244: '=' : conversion from 'UINTN' to 'UINT16', possible loss of data
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalConIn.c(1594) : warni
ng C4244: '=' : conversion from 'UINTN' to 'UINT16', possible loss of data
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0
\Vc\bin\x86_amd64\cl.exe"' : return code '0x2'
Stop.

build...
: error 7000: Failed to execute command
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Vc\bin\nmake.exe /no
logo tbuild [f:\edk2\Build\MdeModule\DEBUG_VS2013x86\X64\MdeModulePkg\Universal\
Console\TerminalDxe\TerminalDxe]

build...
: error F002: Failed to build module
f:\edk2\MdeModulePkg\Universal\Console\TerminalDxe\TerminalDxe.inf [X64,
VS2013x86, DEBUG]

- Failed -
Build end time: 13:42:27, Jul.16 2015
Build total time: 00:01:22

f:\edk2>

Appreciate your help

Thanks,
Tony

Andrew Fish

2015-07-10 00:29:25 UTC

Permalink

This post might be inappropriate. Click to display it.

Continue reading on narkive:

Search results for '[edk2] edk2 build problems' (Questions and Answers)

replies

should i marry this guy ? is there any chance he will change?

started 2010-05-17 10:40:47 UTC

marriage & divorce