Hi Yehuda,
The current version of the EDK II BaseTools does not support this. For the time
being, wrapping the build command in a batch script is the only method for
calling external tools after a build completes.
We would like to introduce two new entries to the [Defines] section of the DSC
1. The exception message maybe printed by DebugLib. Release/Production image
use NULL DebugLib instance. It may make sense without output on serial port.
2. "Already started" makes sense due to CPU driver has already registered its
own exception handler.
Your order to unregister with NULL
Reviewed-by: Liming Gao
-Original Message-
From: Zeng, Star
Sent: Monday, December 28, 2015 1:39 PM
To: edk2-devel@lists.01.org
Cc: Gao, Liming
Subject: [PATCH] MdeModulePkg Variable: Handle ftw driver executes prior to
variable driver
Variable driver uses
Reviewed-by: Liming Gao
-Original Message-
From: Zeng, Star
Sent: Monday, December 28, 2015 2:01 PM
To: edk2-devel@lists.01.org
Cc: Gao, Liming
Subject: [PATCH] MdeModulePkg Variable: Add a missing variable info record
Cc: Liming Gao
Hello everyone
I am searching for a builtin mechanism to run a post build script in EDK2
i need to wrap my FD file with a specific header that is required by the boot
firmware of my device
?Is there any generic way to run a post build script in EDK2 or must i resort
to writing my own
Reviewed-by: Yonghong Zhu
Best Regards,
Zhu Yonghong
-Original Message-
From: Chen, Hesheng
Sent: Tuesday, December 29, 2015 3:30 PM
To: Zhu, Yonghong; edk2-devel@lists.01.org
Subject: [BaseTool][UPT]Fix a typo issue
Hello Yonghong and all,
Could you help
1. I actually don't get any prints when I do that
2. I get "Already started" error from the RegisterInterruptHandler when I
try to register my own handler, and again I don't get any prints.
On Tue, Dec 29, 2015 at 3:04 AM, Fan, Jeff wrote:
> Got you.
>
>
>
> Could you try
7 matches
Mail list logo