Re: [edk2] [PATCH 1/9] ArmPlatformPkg/ArmVExpressPkg: Add support for EDK2_OUT_DIR build parameter

Subject: Re: [edk2] [PATCH 1/9] ArmPlatformPkg/ArmVExpressPkg: Add support for EDK2_OUT_DIR build parameter

From: Andrew Fish <afish@apple.com>

To: Tom Rini <trini@ti.com>

Date: 2013-06-22 01:57:13


On Jun 21, 2013, at 2:02 PM, Tom Rini  wrote:

>> Another solution would be to introduce an environment variable (eg:
>> EDK_BUILD_PATH) set by edksetup.(sh|bat) with a default value equal to
>> $(WORKSPACE) that can be overwritten.
> 
> I suspect this would work for everyones use cases.
> 

This might actually be a bigger change to the tools as it impacts all the generated makefiles. But then again with all the complexity of the build.py it may be easier to hack up the makefile templates? 

>> But I am not sure to fully understand the motivation behind changing the
>> default build directory. If you cannot add pre/post action to your build
>> system then it should not take a long time to receive a new request to
>> change the UEFI firmware filename ;-)
> 
> Allowing for user-specified output directories helps a lot of different
> use cases.  My favourite is when debugging builds and bisecting a
> problem to throw each build into foo.rev so that I can if needed compare
> objects, etc, etc, without having to think about moving stuff around.

OK now I'm sold on this concept. I could see adding a check in the platform build script and override build results directory if I'm on a git branch other than master. 

Thanks,

Andrew Fish

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel