From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=pass header.i=@akeo-ie.20150623.gappssmtp.com header.s=20150623 header.b=1kiWV4jf; spf=none, err=permanent DNS error (domain: akeo.ie, ip: 209.85.208.51, mailfrom: pete@akeo.ie) Received: from mail-ed1-f51.google.com (mail-ed1-f51.google.com [209.85.208.51]) by groups.io with SMTP; Wed, 08 May 2019 03:25:52 -0700 Received: by mail-ed1-f51.google.com with SMTP id m4so21578193edd.8 for ; Wed, 08 May 2019 03:25:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akeo-ie.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=aDH0G9VNfmWKx09kBEkVBG9Mm1XpuGwFFwNRfcLXz3s=; b=1kiWV4jf+kVVOLwSP85dVh1jaQJOHDwf8h8BPhTJMniOWYmtiZKl5ztOHX2wdtV6Z/ ob9jcU4CCSbJFWwiq8Lv1Mrvo5rtEeamaauD2Z4ybVbwcO1n5yQUZIWK/n3nYm4Nmr3e BiM7FhT7tDa4RPy6QYMsSUy86q0Uvh9tC/xYfA8xfudw+GLRbKh51dUoLvUBqTmw1ySc 4zOK6q3ZVyNCVE1CN4TuGiTgW/jGgHZ8jRClO913J8EfH9c3ygzmKIkmTa6X9lcZGVLS abgBR4zW5RiEAQ6sbt+AkIRUDmI02yhH2Z9mgv/bSJ1xPBrF1mgsh77XqH7uSoruigK4 v5yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=aDH0G9VNfmWKx09kBEkVBG9Mm1XpuGwFFwNRfcLXz3s=; b=lqteBxT5H94x8nim1R2dUHWoVbBhFLRkIpKC9uLypdi7KBkbeuFiF3Oqcs6m8Qi406 IukBPzUUvMlOjEE412BCo69ONpqyg5Q4BhwA9oPbOYT1R3jSx8wKM6IW3wYjVFTbak9e fbBuUV0Tiv2vP3VpfVeT/P9wPYyDa4lW5hC5bbpAaWxVSVmMXy2yzV79+t0E3gUdmGIK 78KbRq/VnixaFnDPjoPdZagL21UaWcpdp7yBkZuQnLsEggyscHP5p0Oh/cn/n6fby6uf RsvVJBvG48FwuEim82LEKYlFqtq8WWj9uvA0z5NF5anK6COnPeaU2b7BCRJXukY24qGr C1DA== X-Gm-Message-State: APjAAAVmh8bXqbIm5yG+f+k/sSOxCel5cHD9Hf7pbuG+og2EFPXb5FbF 6Nhe63alYPdSvdRDrmJUwAGfSQ== X-Google-Smtp-Source: APXvYqxGrnnkWiElUHOG9sd3aEDcFFUfFhCVBrO9IN4W/aQTM5C+5lFvvh546HJl2oWIe15odLPWxg== X-Received: by 2002:a50:b854:: with SMTP id k20mr8673695ede.224.1557311150902; Wed, 08 May 2019 03:25:50 -0700 (PDT) Return-Path: Received: from [10.0.0.122] ([84.203.71.1]) by smtp.googlemail.com with ESMTPSA id e4sm2570811ejm.50.2019.05.08.03.25.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 May 2019 03:25:49 -0700 (PDT) Subject: Re: [edk2-devel] tool chain tag setting for vs2017 To: devel@edk2.groups.io, francisco_flynn@foxmail.com References: From: "Pete Batard" Message-ID: <46fb43d9-dfdc-a481-f60b-d5f362ed2c0b@akeo.ie> Date: Wed, 8 May 2019 11:25:48 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=gb18030; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit Hi Flynn, On 2019.05.08 09:00, "ÐìÁÖ wrote: > Hey guys, > > I may found a problem here.. > > I'm trying to build tianocore with visual studio 2017, the tianocore > commit id is > df7c81b5b219c9aee776baa466dd64c9d318dd80(Tue Apr 30 10:16:01 2019), > after seting up the build environment and change TOOL_CHAIN_TAG to VS2017x86 > according from > https://github.com/tianocore/tianocore.github.io/wiki/Windows-systems-ToolChain-Matrix The first thing that needs to be pointed out is that the ToolChain-Matrix has not been updated for VS2017, so you need to be careful about extrapolating what applies for VS2015 or VS2013 to VS2017. > , then build, the process will terminate with error message: > *[VS2017x86] not defined. No toolchain available for build! * Indeed. That's because we are now using a separate VS2017_HOST (currently set to 'x86' by default) to identify the architecture of the host platform tools, so we're not using VS2017x86 any more. > After several tries, i change TOOL_CHAIN_TAG to *VS2017 *instead of > VS2017x86, > then the problem solved, i'm not sure if vs2017 setting is inconsistent > with vs2015 or vs2010.. > or i have wrong setting somewhere else? You should just use VS2017. And of course, we'll need to update the Matrix to make that information public as well. If you are seeing issues after setting TOOL_CHAIN_TAG to VS2017, please let us know. Regards, /Pete