Sean,

I agree the hard coded paths are not good. This was a quick workaround to see if I could get the Azure Pipeline agents to function. It we continue this path, we would have to migrate those out to something like toolsdef.txt or other mechanism that is more flexible.

There is a fundamental assumption that all edk2 build environments support a host POSIX build. It would be better to update Azure Pipelines config to meet this assumption, and I can abandon this patch with the hard coded paths.

Do you have a suggestion for a patch to the Azure Pipelines YAML files to setup the VS host env?

Thanks,

Mike

From: sean.brogan via [] <sean.brogan=microsoft.com@[]>
Sent: Friday, January 31, 2020 4:33 PM
To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [Patch] BaseTools/Build: Fix Structured PCD app host env issues

Mike,
The hardcoded vs paths are not a safe assumption. 
I would rather see agreement of how the environment should be configured prior to calling edk2 build and if being capable of building host os specific binaries is the requirement then that should be clarified and the scripts can be updated.  That way this type of stuff is contained within environment specific scripts rather than the edk2 build system.  

thanks
Sean