Re: Having problems when trying to instrument all code of a specific UEFI driver (including the library code)
Mick,toggle quoted messageShow quoted text
Are you trying to do runtime or static analysis? That would help guide my answers.
What your are are doing in the INF file you can generally do in the DSC file too per driver. There is the concept of override of things per single INF file entry in the DSC . This syntax include <BuildOptions> and pointing at alternate libraries for just those drivers. If you have common libs that you need 2 flavors of you could fork a copy and point to those from the per driver entries in the DSC, for the drivers that you care about. Conceptually you could fork a DSC file, or !if def your DSC file to support multiple modes (normal and analysis) of build.
We added the overrides to the DSC file so your platform could override things without having to override the driver source (or INF) that you might have gotten from a vendor. Thinking act would be easier to maintain over the long run, and easier to merge changes from updates to the vendor code.
!if $(NETWORK_IP6_ENABLE) == TRUE
Anyway always happy to help folks brainstorm on the easiest way to do things. Sometimes with the edk2 it is not always obvious….
On Apr 10, 2021, at 5:19 AM, firstname.lastname@example.org wrote: