I'm seeing this issue building edk2 with GCC on Windows - in this case Aarch64
but I think the issue may be common to all gcc-on-Windows situations.
tools_def has this stuff for bypassing the objcopy stage:
*_*_*_OBJCOPY_PATH = echo
*_*_*_OBJCOPY_FLAGS = objcopy not needed for
But echo gets quoted which bypasses the evaluation of the internal commands for
cmd.exe:
1> "echo" objcopy not needed for
c:\edk2\Build\ArmVExpress-FVP-AArch64\DEBUG_GCC49\AARCH64\MdeModulePkg\Universal\PCD\Dxe\Pcd\DEBUG\PcdDxe.dll
1> '"echo"' is not recognized as an internal or external command,
1> operable program or batch file.
It seems like a more robust solution is needed for GCC on Windows.
Eugene
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel