Question about PACKAGES_PATH

Question about PACKAGES_PATH

[Abner Chang]

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

Hi all,
I encountered a weird build issue when I use PACKAGES_PATH for the package outside WORKSPACE.
Currently I have RedfishClientPkg in the different repo and I configure PACKAGES_PATH as below,
Set PACKAGES_PATH=d:\edk2; d:\edk2-redfish-client

I always get the build error as below,
;-------------------------------------------------------------------------

build.py...
: error 7000: Failed to execute command
        E:\Program Files (x86)\Microsoft Visual Studio 14.0\Vc\bin\nmake.exe /no
logo tbuild [d:\edk2\Build\EmulatorX64\DEBUG_VS2015x86\X64\edk2-redfish-client\R
edfishClientPkg\RedfishFeatureCoreDxe\RedfishFeatureCoreDxe]


build.py...
: error 7000: Failed to execute command
        E:\Program Files (x86)\Microsoft Visual Studio 14.0\Vc\bin\nmake.exe /no
logo tbuild [d:\edk2\Build\EmulatorX64\DEBUG_VS2015x86\X64\edk2-redfish-client\R
edfishClientPkg\Converter\AccountService\v1_0_0\RedfishAccountService_V1_0_0_Dxe
]


build.py...
: error F002: Failed to build module
        d:\edk2-redfish-client\RedfishClientPkg\RedfishFeatureCoreDxe\RedfishFea
tureCoreDxe.inf [X64, VS2015x86, DEBUG]

;-------------------------------------------------------------------------


However, the build error is gone if I change the naming of external directory to any that doesn't contain "edk2" pattern in the folder name, such as "xxxx" or "edkii-redfish-client".
Is this a known issue? Anyone has the similar experience?

Thanks
Abner

[-- Attachment #2: Type: text/html, Size: 4741 bytes --]

Re: [edk2-devel] Question about PACKAGES_PATH

[Laszlo Ersek]

On 05/03/21 03:55, Abner Chang wrote:
> Hi all,
> 
> I encountered a weird build issue when I use PACKAGES_PATH for the
> package outside WORKSPACE.
> 
> Currently I have RedfishClientPkg in the different repo and I configure
> PACKAGES_PATH as below,
> 
> Set PACKAGES_PATH=d:\edk2; d:\edk2-redfish-client
> 
>  
> 
> I always get the build error as below,
> 
> ;-------------------------------------------------------------------------
> 
>  
> 
> build.py...
> 
> : error 7000: Failed to execute command
> 
>         E:\Program Files (x86)\Microsoft Visual Studio
> 14.0\Vc\bin\nmake.exe /no
> 
> logo tbuild
> [d:\edk2\Build\EmulatorX64\DEBUG_VS2015x86\X64\edk2-redfish-client\R
> 
> edfishClientPkg\RedfishFeatureCoreDxe\RedfishFeatureCoreDxe]
> 
>  
> 
>  
> 
> build.py...
> 
> : error 7000: Failed to execute command
> 
>         E:\Program Files (x86)\Microsoft Visual Studio
> 14.0\Vc\bin\nmake.exe /no
> 
> logo tbuild
> [d:\edk2\Build\EmulatorX64\DEBUG_VS2015x86\X64\edk2-redfish-client\R
> 
> edfishClientPkg\Converter\AccountService\v1_0_0\RedfishAccountService_V1_0_0_Dxe
> 
> ]
> 
>  
> 
>  
> 
> build.py...
> 
> : error F002: Failed to build module
> 
>        
> d:\edk2-redfish-client\RedfishClientPkg\RedfishFeatureCoreDxe\RedfishFea
> 
> tureCoreDxe.inf [X64, VS2015x86, DEBUG]
> 
>  
> 
> ;-------------------------------------------------------------------------
> 
>  
> 
>  
> 
> However, the build error is gone if I change the naming of external
> directory to any that doesn’t contain “edk2” pattern in the folder name,
> such as “xxxx” or “edkii-redfish-client”.
> 
> Is this a known issue? Anyone has the similar experience?

I've not met this build issue yet, but I do suggest the following setup
anyway:

PACKAGES_PATH=d:\edk2;d:\edk2-redfish-client
WORKSPACE=d:\edk2-build

and make sure that the "Conf" subdir exists in $WORKSPACE before you run
"edksetup.bat".

At least this is (conceptually) what I use (on Linux).

Keeping the Build and Conf directories out of the main edk2 checkout is
good.

Thanks
Laszlo