From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.120]) by mx.groups.io with SMTP id smtpd.web10.8890.1589964155992157108 for ; Wed, 20 May 2020 01:42:36 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Be65EdQb; spf=pass (domain: redhat.com, ip: 205.139.110.120, mailfrom: philmd@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589964155; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KwECEKm0MGY+vr833do5g/68eOIPq3sD6EGT7rc7Xo4=; b=Be65EdQbHx59fd10qG68ZqKqnE8vlkREtE+jNCrpYVguirEqx4R5jdAyhFhGhxKFFYUlEi 0PsSXeVhvdm8ifFY2TmYP7Rj9BLiC2lq8vKFccgV6DWBkj+H5M8PI0uSMc0EVmTWt79Zvo bATHmTtz0VHJz13GAJT0c3A3umzcZzw= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-320-KIlHSDMKOoWrUho9dG1V4A-1; Wed, 20 May 2020 04:42:31 -0400 X-MC-Unique: KIlHSDMKOoWrUho9dG1V4A-1 Received: by mail-wm1-f72.google.com with SMTP id a206so634484wmh.6 for ; Wed, 20 May 2020 01:42:31 -0700 (PDT) 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=KwECEKm0MGY+vr833do5g/68eOIPq3sD6EGT7rc7Xo4=; b=m1vQ/mSVe5RS6+le3zTGL9yBE/+2sF69nI1drhXMDBW5l5B6MfnXR6+HE8jLcdM/a1 27A4UMFf6y9mGulxjN+o5iLf+neePP7XEZxtCcisxioMK3cw9fENZMkDTDDbqLkjrsTk PBKoA46hYArx9NyCBocTAq8T75M5U19UJPL7kvLVlTEM+d/TMsE7lLOQsoOhr6tYUw7f NdnShWCF9pTcmImSqXu/hLbE+ppu8FuLzGf0YsVM27xQSfO7tW0xLV3/oUdQciSH5sH4 fbOWtaXbe1g594oIXv1VanZNhxuH3TXqInGdDTndT/jtGTDz+hwjJNnnKrO8U3UgF70K 0/WQ== X-Gm-Message-State: AOAM532VSVCKwFWW6OHcJD7acqThxRum3keagbCl+Vn8GBrlV9QR6VTq RCMgF3QJ+UB7qAqk3f5bFluymTSPU9Gi9LKqWYq2U2MdcPhb6SyG8uFanjBaoIEpzqIeNGe1Ldp yM8SA72gdSQgN1g== X-Received: by 2002:a1c:3984:: with SMTP id g126mr3476917wma.169.1589964150044; Wed, 20 May 2020 01:42:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxYKk7Y9QRBaIM+k2YwjNGtAuFXVxQhFjOSV+tT5xmHd63d5tzDDhZ2l5MsxnirWTnTvKo05w== X-Received: by 2002:a1c:3984:: with SMTP id g126mr3476893wma.169.1589964149817; Wed, 20 May 2020 01:42:29 -0700 (PDT) Return-Path: Received: from [192.168.1.38] (17.red-88-21-202.staticip.rima-tde.net. [88.21.202.17]) by smtp.gmail.com with ESMTPSA id y185sm2324086wmy.11.2020.05.20.01.42.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 May 2020 01:42:29 -0700 (PDT) Subject: Re: [edk2-devel] Official way to build BaseTools - Edk2ToolsBuild.py? To: devel@edk2.groups.io, spbrogan@outlook.com, rebecca@bsdio.com References: <5eed935b-7a4c-dffb-0643-d7bcf8499202@bsdio.com> From: =?UTF-8?B?UGhpbGlwcGUgTWF0aGlldS1EYXVkw6k=?= Message-ID: <16768bbe-b73d-f5a3-5afb-8047c9bc0b53@redhat.com> Date: Wed, 20 May 2020 10:42:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Sean, On 5/20/20 5:36 AM, Sean wrote: > I am not sure what the community wants to do with it.  It was created > for the CI build so it is tailored to the needs of the CI build but I > have no problem with updates. FWIW I find it useful to reproduce CI failure locally and debug them (usually offline, with no access to CI for some time). > > I agree with your feedback and see no reason either of those would be a > problem for the CI use case. > > Although not convenient for local builds it does currently output full > build log to BaseTools/BaseToolsBuild/BASETOOLS_BUILD.txt. > > Thanks > Sean > > > > > > > On 5/19/2020 8:23 PM, Rebecca Cran wrote: >> I'm wondering if using BaseTools/Edk2ToolsBuild.py will become the >> official/standard way users are expected to build BaseTools? If so, >> there are a few problems that I'd like to see fixed, which I'll see if >> I can find some time to work on. >> >> >> For example: on Linux, running it without arguments gives "ValueError: >> Bad VC" - because it defaults to the VS2017 toolchain. >> >> If you break something in BaseTools and so it fails to build, it >> prints "Exception: Failed to build." with no further details. >> >> >> I'd like to improve it so it detects being run on a non-Windows >> platform and tries to use GCC, Clang etc. - and perhaps also to add a >> '--verbose' argument that can be used to give a more specific error >> message when it fails. >> >> > > >