From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, thomas@monjalon.net,
andremue@linux.microsoft.com,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH] ci: build with MSVC in GHA
Date: Tue, 18 Feb 2025 08:32:26 -0500 [thread overview]
Message-ID: <f7teczvbcph.fsf@redhat.com> (raw)
In-Reply-To: <20250213075010.2670431-1-david.marchand@redhat.com> (David Marchand's message of "Thu, 13 Feb 2025 08:50:10 +0100")
David Marchand <david.marchand@redhat.com> writes:
> Add a build target in Windows 2022 for MSVC.
>
> Loading MSVC environment and having successive commands in a single
> (cmd or pwsh) shell does not seem to correctly report if one of the
> commands failed.
> For now, load MSVC environment and run commands in separate shells.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
LGTM.
Acked-by: Aaron Conole <aconole@redhat.com>
How far back will this work (ie: can we backport this to older branches?)
> .github/workflows/build.yml | 38 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
> index dcafb4a8f5..aef692ca1f 100644
> --- a/.github/workflows/build.yml
> +++ b/.github/workflows/build.yml
> @@ -174,6 +174,44 @@ jobs:
> build/meson-logs/meson-log.txt
> build/meson-logs/testlog.txt
>
> + windows-vm-builds:
> + name: ${{ join(matrix.config.*, '-') }}
> + runs-on: ${{ matrix.config.os }}
> + strategy:
> + fail-fast: false
> + matrix:
> + config:
> + - os: windows-2022
> + compiler: msvc
> +
> + steps:
> + - name: Checkout sources
> + uses: actions/checkout@v4
> + - name: Set up Python
> + uses: actions/setup-python@v5
> + with:
> + python-version: '3.x'
> + - name: Install dependencies
> + run: python -m pip install meson==1.6.1 ninja
> + - name: Configure
> + shell: cmd
> + run: |
> + call "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" -host_arch=amd64 -arch=amd64
> + meson setup -Denable_stdatomic=true build
> + - name: Build
> + shell: cmd
> + run: |
> + call "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" -host_arch=amd64 -arch=amd64
> + meson compile -C build
> + - name: Upload logs on failure
> + if: failure()
> + uses: actions/upload-artifact@v4
> + with:
> + name: meson-logs-${{ join(matrix.config.*, '-') }}
> + path: |
> + build/.ninja_log
> + build/meson-logs/meson-log.txt
> +
> prepare-container-images:
> name: ${{ join(matrix.config.*, '-') }}
> runs-on: ubuntu-latest
next prev parent reply other threads:[~2025-02-18 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 7:50 David Marchand
2025-02-18 13:32 ` Aaron Conole [this message]
2025-02-18 14:10 ` David Marchand
2025-02-18 15:35 ` Andre Muezerie
2025-02-19 8:09 ` David Marchand
2025-02-18 19:45 ` Aaron Conole
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-all 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=f7teczvbcph.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=andremue@linux.microsoft.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).