Liming,
> The GCC binary
> tools is got from
> https://sourceforge.net/projects/edk2developertoolsforwindows/file
> s/Tool%20Chain%20Binaries/. If you only use gcc ARM, you can set
> GCC49_DLL=%UEFI_BUILD_TOOLS%\gcc492-
> arm\bin\;%UEFI_BUILD_TOOLS%\gcc492-arm\dll\
This is my issue. I obtained a Linaro AArch64 GCC toolchain along with a mingw
make variant and neither provide echo.exe as you have in this distribution.
Thanks for the pointer, I never would have found this on my own.
Silly question: Since I think this is the first time I've seen the
edk2developertoolsforwindows project, do you think it would make sense to put a
reference to it in the BaseTools/ReadMe.txt, BaseTools/BuildNotes.txt, or
BaseTools/building-gcc.txt?
Andrew,
> My thinking is the generated GNUmakefiles assume a non Windows
> command line tools.
In my experience this isn't the case - the rest of the make works fine with
standard cmd.exe. As Liming pointed out, echo is provided by a echo.exe tool.
Looking at my tree I am indeed getting 'Makefile' presumably because of this
stuff in GenMake.py:
if sys.platform == "win32":
gMakeType = "nmake"
else:
gMakeType = "gmake"
and then
_FILE_NAME_ = {
"nmake" : "Makefile",
"gmake" : "GNUmakefile"
}
but we're still calling GNU make because of the tools_def rule:
*_GCC49_*_MAKE_PATH = DEF(GCC49_IA32_PREFIX)make
So I guess it's a hybrid of windows-shell + GNU make that makes it all work.
You can see it in a generated makefile:
#
# Shell Command Macro
#
RD = rmdir /s /q
RM = del /f /q
MD = mkdir
CP = copy /y
MV = move /y
Well... now I learned TWO new things today, and the day is still early...
Eugene
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
