Re: [edk2] UDK2010.SR1 build help

Subject: Re: [edk2] UDK2010.SR1 build help

From: padmarao edapalapati <>


Date: 2012-04-12 18:00:21

Hi Jordan,

I think Raghu was trying these things on ubuntu machine

After execution of Basetools command, i tried to see WORKSPACE and EDK_TOOLS_PATH values with echo $WORKSPACE and echo $EDK_TOOLS_PATH commands but those command returns null, that means is not setting paths.


On Wed, Apr 11, 2012 at 11:41 PM, Jordan Justen <> wrote:
On Wed, Apr 11, 2012 at 04:25, padmarao edapalapati
<> wrote:
> Hi,
> There is bug in present so follow the below steps then you will
> able to run build command.
> export WORKSPACE="Workspace root directory"
> "Workspace root directory" is your edk2 root directory path, do not use
> double quotes. For Example export WORKSPACE=/home/administrartor/edk2
> export EDK_TOOLS_PATH="Workspace root directory"/BaseTools
> then go to Workspace root directory run ./ BaseTools/
> make -C BaseTools
> Go to BaseTools/Bin/CYGWIN_NT-5.1-i686 directory then execute chmod +x *

Did you download the edk2 tree with windows svn rather than cygwin
svn? That might explain why the scripts are not marked as executable.

> export PATH=${PATH}:/"Workspace root
> directory"/BaseTools/Bin/CYGWIN_NT-5.1-i686/

So, these steps do not work for you?
1. export EDK_TOOLS_PATH=/path/to/edk2/BaseTools
2. ". BaseTools" (without the quotes)
"source BaseTools" should work too.

What does 'uname -sm' under cygwin show for you? If it is not
something like CYGWIN_NT-5.1-i686, then that could be part of it. But,
edk2 r13178-13180 should fix this issue too.


Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
edk2-devel mailing list