Jordan Justen [mailto:[email protected]] wrote:
]On Tue, Oct 21, 2014 at 1:22 AM, Gao, Liming <[email protected]> wrote: ]> Scott: ]> I will download them and try again. ]> ]> For the patch, I provide another compatible version in previous mail. Have you any comment for it? ]> ]> Linux user doesn't need to set GCC49_BIN, GCC49_DLL env, because /usr/bin/ is the default system PATH. Windows user need to set ]GCC49_BIN, GCC49_DLL and IASL_PREFIX env to use this tool chain. ]> Index: Conf/tools_def.template ]> =================================================================== ]> --- Conf/tools_def.template (revision 16124) ]> +++ Conf/tools_def.template (working copy) ]> @@ -182,8 +182,8 @@ ]> DEFINE GCC48_IA32_PREFIX = /usr/bin/ ]> DEFINE GCC48_X64_PREFIX = /usr/bin/ ]> ]> -DEFINE GCC49_IA32_PREFIX = /usr/bin/ ]> -DEFINE GCC49_X64_PREFIX = /usr/bin/ ]> +DEFINE GCC49_IA32_PREFIX = ENV(GCC49_BIN) ]> +DEFINE GCC49_X64_PREFIX = ENV(GCC49_BIN) ] ]How about using GCC_BIN for the environment variables? ] ]I don't think we need the full toolchain name, because I don't think ]we'll need to set the prefix separately for multiple toolchains for a ]single build. (Since the EDK II build command only allows a single ]toolchain.) ] ]But, I guess it doesn't make too much difference. ] ]-Jordan GCC_BIN and GCC_DLL seem OK to me for the reason you point out. Either way gives the Windows user freedom over the location of gcc build tools. Thanks, Scott ]> -*_GCC49_*_MAKE_PATH = make ]> +*_GCC49_*_MAKE_PATH = DEF(GCC49_BIN)make ]> +*_GCC49_*_*_DLL = DEF(GCC49_DLL) ]> *_GCC49_*_ASL_PATH = DEF(UNIX_IASL_BIN) ]> ]> Thanks ]> Liming ]> -----Original Message----- ]> From: Scott Duplichan [mailto:[email protected]] ]> Sent: Tuesday, October 21, 2014 1:14 PM ]> To: [email protected] ]> Subject: [edk2] EDK2 Developer Tools for Windows ]> ]> Here are Windows hosted gcc tool chains for EDK2 builds: ]> ]> https://sourceforge.net/projects/edk2developertoolsforwindows/files/ ]> ]> I will add more readme files tomorrow. ]> ]> The tools build IA32, X64, IPF, ARM, and AARCH64 from Windows. X64 builds are well tested. I have not yet boot tested IA32 ]builds but plan to. I don't have a way to boot test IPF, ARM, and AARCH64 builds. ]> ]> Only gcc 4.9.1 tool chains are uploaded. Older gcc versions can be built if needed. A patch is included to add support for ]IA32, X64, ARM, and AARCH64. If there is any interest in IPF it can be added too. ]> ]> This patch "breaks" non-Windows builds. The fix is to execute: ]> ]> export GCC49_X86=/usr ]> ]> .. before building. I think logic needs to be added to edksetup.sh to set GCC49_X86 if it is not already set. Linux guys, what ]is the best way? ]> ]> Thanks, ]> Scott ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
