Re: edk2toolext based build workspace question

Jeff Brasen

Basically, the workspace directory that is used in the scripts seem to assume that there are files under there already, as opposed to just an out directory as we use it and use packages path to search everything. It seems to search for a bunch of things based on that prior to calling the edk2 build subsystem. I think we found another way to support that with our CI system so I think I can work with the current behavior.



From: <> on behalf of Sean via <spbrogan@...>
Sent: Tuesday, July 6, 2021 8:55 PM
To: <>; Jeff Brasen <jbrasen@...>
Subject: Re: [edk2-discuss] edk2toolext based build workspace question

External email: Use caution opening links or attachments

Can you elaborate more on what you have tried. What files are causing problems? The build output should be handled the same as any edk2 build

From: <> on behalf of Jeff Brasen <jbrasen@...>
Sent: Tuesday, July 6, 2021 9:14:14 AM
To: <>
Subject: [edk2-discuss] edk2toolext based build workspace question

I am looking at converting our build from using a bunch of custom scripts/makefiles around the UEFI build process to the edk2toolext based python builder and am running into an Issue. Our overall build automation system whats to keep the source directory unchanged with all build output in another directory. I am supporting this currently by having WORKSPACE point to the specified out directory and PACKAGES_PATH pointing to our source. However if I have workspace point somewhere else with edk2toolext it seems like it requires the workspace to be with the sources. Is this something that can be done or is just a limitation/design feature of this build system?


Join to automatically receive all group messages.