Hi, I assume that you are using linux because you're talking about ELF files. MinGW may be able to compile PE images in Linux but tbh there's no reason for that and the "freaking" translation is actually a pretty good implementation and works very well.
As for the kind of toolchain to use: there's always (at least) two types: bare metal toolchains(arm-eabi,arm-none-eabi, aarch64-elf), and the ones with a OS ABI(androideabi, linux-gnueabi,linux-gnueabihf, ...). While unlike other bootloader/kernel projects EDK2 seems to work with all of them I can only recommend using the bare metal variants. For ARM and AArch64 I recommend using linaro's latest stable release(5.3 at the time of writing): http://www.linaro.org/downloads/ sometimes the website is out of date and you can go here directly: https://releases.linaro.org/components/toolchain/binaries/ I've also CC'ed the Arm maintainers so you'll actually get answers unlike me when I asked the same question about a year ago ;) Thanks Michael On Tue, Aug 9, 2016 at 2:29 AM, valerij zaporogeci <vlrzpr...@gmail.com> wrote: > Sorry for the really dumb question, but I wanted to ask you. What > compilers/tools you are using for building your UEFI/PI implementation > on arm (both aarch32 (armv7) and aarch64)? And generally, is there a > toolchain (available for downloading (not necessarily free) in binary > form) for the arm architecture able to make PE/COFF images natively, > without freaking translation from elf? > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
