From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mx.groups.io with SMTP id smtpd.web10.7514.1684196505864823073 for ; Mon, 15 May 2023 17:21:46 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@bsdio.com header.s=fm2 header.b=QtyknA62; spf=pass (domain: bsdio.com, ip: 66.111.4.27, mailfrom: rebecca@bsdio.com) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2A7825C01C6; Mon, 15 May 2023 20:21:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 15 May 2023 20:21:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdio.com; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:message-id:mime-version:reply-to :sender:subject:subject:to:to; s=fm2; t=1684196505; x= 1684282905; bh=mbRl26ON1FBgjfLI5TG46/PtBTK63epnb2CySe9cw4E=; b=Q tyknA62fuvjms451MthlKLk8LHKZxVc+De3gGX1Jq02fzCfbi7LwYQpCW0ziIKal f9qRK9zsEY8jwaZLvvcCO9pDuYkYasg7VTeWiJ3E0exm9S5h3+RiWcFkff5nfWdK SxlKL6Vq8aBzto86xSSjZgyxpdZynUV4jRcO5ixg9EMQA2qOM7pzQ6XoEAjrTlhK 9LN3KnBxw3+9+bjlbNz7k3lxRiz5FewKGX/5PNn3GUb5kJcwfEKhnZNa7p1+2iyJ f4aPJTY+vuZo8hYJ+q65763uC7/AGrdXqB0TMQWOTaGhqmEDLMm/RWiA2DHqqoZg 2gE626l8XWBubK2cvRtvw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1684196505; x=1684282905; bh=m bRl26ON1FBgjfLI5TG46/PtBTK63epnb2CySe9cw4E=; b=JLGcQEUmCWzMONYWA Mqn0IdOKPAxcuHw6SheyjNN5jBUfTOLK5+doo2tD4+0phBqmTbr1fQNTWQ8JhDVh pApHsH3+SBY6h48QamvCmaIz3LQKt4bXOn0Gq21Y4H8TfhmxtJYFsvWd3hmKgNh3 RlqXJtHIKsEFdU5m8P+Yx+XtQg9F0xd/4zediF3vaUefVDzVU0IVFTHQ6fLYurfu S5lLDt5qxSMkqpbHgBt2rYZhaHMPArEJU+mNiVxLD68kns1+NfPgc9o2k2dDXz5I jVC8Xg/vEOmbjMArakFEKfyC2uq6oCtJmEutBb+KKR1GX/UHtsXoWCvGKEIAcFH2 KY7Cw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeehkedgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfvffhufevtgfgsehtjeertddtfeejnecuhfhrohhmpeftvggsvggt tggrucevrhgrnhcuoehrvggsvggttggrsegsshguihhordgtohhmqeenucggtffrrghtth gvrhhnpedvhffhgeeutdekvdelledvvddtfefhieeuuefhheeivdeggeehieekffekveek hfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehrvg gsvggttggrsegsshguihhordgtohhm X-ME-Proxy: Feedback-ID: i5b994698:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 15 May 2023 20:21:44 -0400 (EDT) Message-ID: <659501b8-981c-6276-a4cf-b97608d6b81a@bsdio.com> Date: Mon, 15 May 2023 18:21:42 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 To: 'Nate DeSimone' From: "Rebecca Cran" Subject: Intel's build_bios.py and PYTHONHOME Cc: "devel@edk2.groups.io" Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I've been starting to use the build_bios.py script in Platform\Intel in edk2-platforms to build images for my UpXtreme board. In my Windows installation, it's complaining that PYTHON_HOME / PYTHONHOME isn't set - but I'm not sure why it expects that because python.exe is in my %PATH% and so could be executed directly. Is setting up PYTHONHOME something that's commonly done in Python installations, and is PATH commonly _not_ updated to include the location of python.exe? I'm trying to figure out if it's a leftover from Python 2.x, or if my configuration is non-standard. -- Rebecca Cran