public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: David Vescovi <dvescovi@tampabay.rr.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: beagleboard build on windows w/vs2015 ..what am I missing?
Date: Thu, 29 Sep 2016 13:13:29 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B47EB32@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <002501d21a37$62a52800$27ef7800$@tampabay.rr.com>

VS2015 has no ARM arch tool configuration in tools_def.txt. So, you have to build ARM with GCC. 

In this link https://sourceforge.net/projects/edk2developertoolsforwindows/files, the pre-built windows binary GCC tool are provided. You can download them, then build ARM arch with GCC on Windows. 

Thanks
Liming
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of David Vescovi
Sent: Thursday, September 29, 2016 5:54 PM
To: edk2-devel@lists.01.org
Subject: [edk2] beagleboard build on windows w/vs2015 ..what am I missing?

C:\edk2>build

Build environment: Windows-post2008Server-6.2.9200

Build start time: 05:37:32, Sep.29 2016

 

WORKSPACE        = c:\edk2

ECP_SOURCE       = c:\edk2\edkcompatibilitypkg

EDK_SOURCE       = c:\edk2\edkcompatibilitypkg

EFI_SOURCE       = c:\edk2\edkcompatibilitypkg

EDK_TOOLS_PATH   = c:\edk2\basetools

EDK_TOOLS_BIN    = c:\edk2\basetools\bin\win32

CONF_PATH        = c:\edk2\Conf

 

 

Architecture(s)  = ARM

Build target     = DEBUG

Toolchain        = VS2015x86

 

Active Platform          = c:\edk2\BeagleBoardPkg\BeagleBoardPkg.dsc

Flash Image Definition   = c:\edk2\BeagleBoardPkg\BeagleBoardPkg.fdf

 

Processing meta-data .......

 

 

build...

: error C0DE: Unknown fatal error when processing
[c:\edk2\MdePkg\Library\BasePcdLibNull\BasePcdLibNull.inf]

 

(Please send email to edk2-devel@lists.01.org for help, attaching following
call stack trace!)

 

(Python 2.7.3 on win32) Traceback (most recent call last):

  File "build\build.py", line 2274, in Main

  File "build\build.py", line 2026, in Launch

  File "build\build.py", line 1861, in _MultiThreadBuildPlatform

  File
"c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\AutoGen\A
utoGen.py", line 3952, in CreateMakeFile

  File
"c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\AutoGen\A
utoGen.py", line 3958, in CreateMakeFile

  File
"c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\AutoGen\G
enMake.py", line 184, in Generate

  File
"c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\AutoGen\G
enMake.py", line 525, in _CreateTemplateDict

  File
"c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\AutoGen\G
enMake.py", line 713, in CommandExceedLimit

KeyError: 'PATH'

 

 

- Failed -

Build end time: 05:37:41, Sep.29 2016

Build total time: 00:00:09

 

 

C:\edk2>

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2016-09-29 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29  9:53 beagleboard build on windows w/vs2015 ..what am I missing? David Vescovi
2016-09-29 13:13 ` Gao, Liming [this message]
2016-09-29 16:18   ` David Vescovi
2016-09-29 16:31     ` Andrew Fish

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=4A89E2EF3DFEDB4C8BFDE51014F606A14B47EB32@shsmsx102.ccr.corp.intel.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