From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id A0B1D823AB for ; Thu, 22 Dec 2016 20:54:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1482468871; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=G5qBe9+CDMkH+a3WwTS3KFSov3N27b1QvBLWexsOkPA=; b=eVG0ZRZRBYqVlwHKOep88obfW6R76Qo5Sr6vHR6tPWegD4AIFPhdYC2p4gKUgWAe W7RhasQpE1+YjpTjsNSUZm+daFdd9oNSjZdUVnzUN49Z4kSgb5Tbd0cSTHYcZawK JMceCZiuMCC18q6Npc4Ac0RPdjuwggfJuw1R5FsREtbVgKk4LqXoKzSywpVc3e/5 yvc8AYYqOykYAVMzGNvOxRr9Prsz+J+TBpoFWjxyCf17ryp23npGvvdNrrrQoIzp eL6U/dgV04niKdkFCPBxosL1bp5Y9p8IPsG+2rLM0m0mN2nniwp7E1XDDikaUAVJ BBiqVJqSn2EiQ4d8suzIIA==; Received: from relay5.apple.com (relay5.apple.com [17.128.113.88]) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id E0.64.07408.30EAC585; Thu, 22 Dec 2016 20:54:31 -0800 (PST) X-AuditID: 11973e15-69bfb70000001cf0-56-585cae0305bc Received: from chive.apple.com (chive.apple.com [17.128.115.15]) by relay5.apple.com (Apple SCV relay) with SMTP id 6A.5B.27929.30EAC585; Thu, 22 Dec 2016 20:54:27 -0800 (PST) MIME-version: 1.0 Received: from [17.153.51.221] by chive.apple.com (Oracle Communications Messaging Server 8.0.1.1.0 64bit (built Jun 15 2016)) with ESMTPSA id <0OIM00IYHGANCA70@chive.apple.com>; Thu, 22 Dec 2016 20:54:25 -0800 (PST) Sender: afish@apple.com From: Andrew Fish Message-id: <0B268819-E944-4867-97BC-2E763AE1597A@apple.com> Date: Thu, 22 Dec 2016 20:54:23 -0800 In-reply-to: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6C3866@shsmsx102.ccr.corp.intel.com> Cc: edk2-devel To: wang xiaofeng , "Gao, Liming" References: <20161216182547.616-1-evan.lloyd@arm.com> <734D49CCEBEEF84792F5B80ED585239D5B836C04@SHSMSX103.ccr.corp.intel.com> <734D49CCEBEEF84792F5B80ED585239D5B8371E1@SHSMSX103.ccr.corp.intel.com> <74D8A39837DF1E4DA445A8C0B3885C503A8C6C52@shsmsx102.ccr.corp.intel.com> <734D49CCEBEEF84792F5B80ED585239D5B839479@SHSMSX103.ccr.corp.intel.com> <74D8A39837DF1E4DA445A8C0B3885C503A8C6CBD@shsmsx102.ccr.corp.intel.com> <74D8A39837DF1E4DA445A8C0B3885C503A8C7026@shsmsx102.ccr.corp.intel.com> <741a147f.4b30.15929bf7db2.Coremail.winggundum82@163.com> <70539f18.53f1.15929e451fd.Coremail.winggundum82@163.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14D6C3866@shsmsx102.ccr.corp.intel.com> X-Mailer: Apple Mail (2.3226) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUi2FAYocu+LibCYMYaJos9h44yW6y4t4Hd 4tuWblYHZo/FK6aweize85LJo3v2P5YA5igum5TUnMyy1CJ9uwSujP+v7jMXfAivaGy/zdbA eMeni5GTQ0LARGLPsuusXYxcHEICexkl/i16xwaT2LVxETNEYiOjRO+tuSwgCV4BQYkfk++B 2cwCYRJr9y+BKrrHKDFxyxWwhLCAuMS7M5uYQWw2AWWJFfM/sEM020js7njCDlHjLHHqzUOw ehYBVYk5m26DbeYEGnrs2VRWiAUaEl9XbwerFxHwk3g/bxELxLIVHBJ7331l7GLkADpVVmL2 Ly+QuITAfTaJYxeaWSYwCs1CcuwsJMdC2FoS3x+1AsU5gGx5iYPnZSHCmhLP7n1ih7C1JZ68 u8C6gJFtFaNQbmJmjm5mnpleYkFBTqpecn7uJkZQhEy3E93BeGaV1SFGAQ5GJR5ehylREUKs iWXFlbmHGKU5WJTEef8ax0QICaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYEzJnPOVe4bKjz9X KvLPcs3zi5yqNjtE9HvrvBm1+1fOlxEuVmncdVA89MoepgDl6Ct5/U9nXurO/OuTePF5wVqJ gmc3z86vWB7Qu1y77M2miRYtUVPceuINPvJaFTG4OC7Kn934//p5w9gLRX2W8f/EF0yTjSnk rjp7boWR9Y0jn2xvVclkHFViKc5INNRiLipOBABN9NXQcQIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCIsWRmVeSWpSXmKPExsUi2FDMr8u8LibC4OoRI4s9h44yW6y4t4Hd 4tuWblYHZo/FK6aweize85LJo3v2P5YA5igum5TUnMyy1CJ9uwSujP+v7jMXfAivaGy/zdbA eMeni5GTQ0LARGLXxkXMELaYxIV769m6GLk4hAQ2Mkr03prLApLgFRCU+DH5HpjNLBAmsXb/ EmaIonuMEhO3XAFLCAuIS7w7swlsEpuAssSK+R/YIZptJHZ3PGGHqHGWOPXmIVg9i4CqxJxN t9lAbE6goceeTWWFWKAh8XX1drB6EQE/iffzFrFALFvBIbH33VfGLkYOoFNlJWb/8prAKDAL yX2zkNwHYWtJfH/UChTnALLlJQ6el4UIa0o8u/eJHcLWlnjy7gLrAka2VYwCRak5iZWmeokF BTmpesn5uZsYwYFeGLGD8f8yq0OMAhyMSjy8DlOiIoRYE8uKK3MPMUpwMCuJ8Louj4kQ4k1J rKxKLcqPLyrNSS0+xDiREejJicxSosn5wDjMK4k3NDExMDE2NjM2Njcxp6WwkjivBV9EhJBA emJJanZqakFqEcxRTBycUg2M8g78jfYcM06ZvOJ7kKJxV+HV79n9TtwJdgLPSjjfMlY3f3+b zsHZtMdY7uDS7w+jg6JPPTx1ZXXlnuQfSz5HJ7x5XyDF66r4xN3s36aJNycJt3WLiX586GB/ 6tafEOlVWcd+GN162RFjMS/r/uUFe07VBMfn8GTsmix1Zt0DV1F249hu5em2SizFGYmGWsxF xYkAsFVVMucCAAA= X-Content-Filtered-By: Mailman/MimeDel 2.1.21 Subject: Re: How to build commonlib of Basetools in x64 mode X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2016 04:54:31 -0000 Content-Type: text/plain; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > On Dec 22, 2016, at 8:39 PM, Gao, Liming wrote: > > Xiaofeng: > BaseTools Windows Makefile (BaseTools\Source\C\Makefile) sets ARCH = IA32. It means BaseTools C tool passes IA32 arch only in Windows OS. I don't try building it with X64 arch. You can update ARCH=X64, and try building BaseTools with 64bit VS compiler. If you meet with warning or error, you can try to clean up them. > The Unix BaseTools makefile build for multiple architectures based on what they detect. So the build should generically be clean for X64. https://sourceforge.net/p/edk2/code/HEAD/tree/trunk/edk2/BaseTools/Source/C/GNUmakefile https://sourceforge.net/p/edk2/code/HEAD/tree/trunk/edk2/BaseTools/Source/C/Makefiles/header.makefile If Windows is hard coded to IA32 lookout for a hard code include path to $(MAKEROOT)/Include/Ia32/ as the Unix makes set that dynamically. Actually it looks like the lower level Windows tries to do the right thing for X64? https://sourceforge.net/p/edk2/code/HEAD/tree/trunk/edk2/BaseTools/Source/C/Makefiles/ms.common !IF "$(ARCH)"=="IA32" ARCH_INCLUDE = $(SOURCE_PATH)\Include\Ia32 BIN_PATH = $(BASE_TOOLS_PATH)\Bin\Win32 LIB_PATH = $(BASE_TOOLS_PATH)\Lib\Win32 SYS_BIN_PATH = $(EDK_TOOLS_PATH)\Bin\Win32 SYS_LIB_PATH = $(EDK_TOOLS_PATH)\Lib\Win32 !ENDIF !IF "$(ARCH)"=="X64" ARCH_INCLUDE = $(SOURCE_PATH)\Include\X64 BIN_PATH = $(BASE_TOOLS_PATH)\Bin\Win64 LIB_PATH = $(BASE_TOOLS_PATH)\Lib\Win64 SYS_BIN_PATH = $(EDK_TOOLS_PATH)\Bin\Win64 SYS_LIB_PATH = $(EDK_TOOLS_PATH)\Lib\Win64 !ENDIF Thanks, Andrew Fish > Thanks > Liming >> -----Original Message----- >> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of >> wang xiaofeng >> Sent: Friday, December 23, 2016 12:16 PM >> To: Andrew Fish >> Cc: edk2-devel >> Subject: Re: [edk2] How to build commonlib of Basetools in x64 mode >> >> HI Fish, >> Thanks for your answer. Actually I am not trying to build base tools . I am >> writing a windows console tool and want to reuse some code of base tools >> common library, All the changes will be in my platform packages, Due to >> some history reason , my own tool is treating UINTN as x64 mode, so will it >> possible to build common.lib in X64 mode? >> Thanks in advance! >> >> >> >> >> >> >> >> >> At 2016-12-23 11:59:38, "Andrew Fish" wrote: >>> The base tools width could be OS Specific so you should not depend on it. In >> other words it has nothing to do with your ROM. You should code tools to >> exact sizes, and only use UINTN if you don't care about size. >>> >>> Sent from my iPhone >>> >>>> On Dec 22, 2016, at 7:35 PM, wang xiaofeng >> wrote: >>>> >>>> Hi Base tool owners, >>>> I tried to build commonlib in basetools . And use the library file in my >> own application tool . I just found the commonlib is build in IA32 mode ,this >> means UINTN is 4 byte in the output lib. I expect to build a X64 mode >> Common.lib ,can you help me? >>>> Or base tools can only run in IA32 mode? >>>> _______________________________________________ >>>> 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 >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel