From: "Jayaprakash, N" <n.jayaprakash@intel.com>
To: devel@edk2.groups.io
Cc: Jayaprakash N <n.jayaprakash@intel.com>,
Rebecca Cran <rebecca@bsdio.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [edk2-devel] [edk2-libc Patch v2 1/1] edk2-libc : add github actions workflow to build PyUEFI using VS2019
Date: Thu, 20 Jun 2024 17:17:27 +0530 [thread overview]
Message-ID: <20240620114908.1610-2-n.jayaprakash@intel.com> (raw)
In-Reply-To: <20240620114908.1610-1-n.jayaprakash@intel.com>
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4788
This commit adds github actions workflow to build python uefi
interpreter with visual studio 2019 tool chain.
The build-python-uefi-vs.yaml file under .github/workflows
implements the build action for building the pyuefi interpreter with
VS2019 tool chain.
Cc: Rebecca Cran <rebecca@bsdio.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Jayaprakash N <n.jayaprakash@intel.com>
Signed-off-by: Jayaprakash N <n.jayaprakash@intel.com>
---
.github/workflows/build-python-uefi-vs.yaml | 84 +++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 .github/workflows/build-python-uefi-vs.yaml
diff --git a/.github/workflows/build-python-uefi-vs.yaml b/.github/workflows/build-python-uefi-vs.yaml
new file mode 100644
index 0000000..a8393d8
--- /dev/null
+++ b/.github/workflows/build-python-uefi-vs.yaml
@@ -0,0 +1,84 @@
+# GitHub actions workflow to build python uefi using VS2019
+#
+# Copyright (c) 2023-2024, Intel Corporation. All rights reserved.
+# SPDX-License-Identifier: BSD-2-Clause-Patent
+#
+
+name: Build Python Interpreter for UEFI using VS2019
+
+on: [push, pull_request]
+
+jobs:
+ build:
+ runs-on: windows-2019
+ env:
+ NASM_PREFIX: "C:\\Program Files\\NASM\\"
+ defaults:
+ run:
+ shell: cmd
+
+ steps:
+ - name: Checkout repository
+ uses: actions/checkout@v4
+
+ - name: Setup Python
+ uses: actions/setup-python@v5
+ with:
+ python-version: '3.10'
+
+ - name: Install NASM
+ run: choco install nasm
+
+ - name: VSWhere
+ run: |
+ "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe"
+
+ - name: Setup environment for Visual Studio 2019 Build Tools
+ run: |
+ "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat" x86
+ set
+
+ - name: Clone EDK2
+ run: |
+ git clone https://github.com/tianocore/edk2.git"
+ cd edk2
+ git submodule update --init
+
+ - name: Build EDK2 Base Tools
+ run: |
+ cd edk2
+ dir
+ edksetup.bat ForceRebuild
+
+ - name: Run srcprep.py
+ run: |
+ echo switching to AppPkg\Applications\Python\Python-3.6.8\
+ cd AppPkg\Applications\Python\Python-3.6.8\
+ dir
+ echo run srcprep.py file
+ python srcprep.py
+
+ - name: Build Python UEFI
+ run: |
+ set PACKAGES_PATH=%CD%\edk2;%CD%;
+ set EDK2_LIBC_PATH=%CD%
+ cd edk2
+ call edksetup.bat
+ build -t VS2019 -a X64 -b RELEASE -p %EDK2_LIBC_PATH%\AppPkg\AppPkg.dsc -D BUILD_PYTHON368
+
+ - name: Create Python UEFI package
+ run: |
+ set WORKSPACE=%CD%\edk2
+ set EDK2_LIBC_PATH=%CD%
+ dir
+ call AppPkg\Applications\Python\Python-3.6.8\create_python_pkg.bat VS2019 RELEASE X64 myUEFIPy
+
+ - name: List build artifacts
+ run: |
+ dir /S edk2\myUEFIPy
+
+ - name: Upload build output as artifact
+ uses: actions/upload-artifact@v4
+ with:
+ name: myUEFIPy-build-VS2019-output
+ path: edk2\myUEFIPy\**\*
--
2.45.1.windows.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119652): https://edk2.groups.io/g/devel/message/119652
Mute This Topic: https://groups.io/mt/106778225/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-06-20 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 11:47 [edk2-devel] [edk2-libc Patch v2 0/1] add github actions workflow to build PyUEFI using VS2019 Jayaprakash, N
2024-06-20 11:47 ` Jayaprakash, N [this message]
2024-06-20 16:21 ` [edk2-devel] [edk2-libc Patch v2 1/1] edk2-libc : " Michael D Kinney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240620114908.1610-2-n.jayaprakash@intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox