From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Cc: david.marchand@redhat.com,
Bruce Richardson <bruce.richardson@intel.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH 0/2] make dpdk buildable with latest msvc
Date: Tue, 17 Oct 2023 06:13:45 -0700 [thread overview]
Message-ID: <1697548427-10153-1-git-send-email-roretzla@linux.microsoft.com> (raw)
This series makes some minor temporary modifications to the MSVC build
to allow DPDK to be buildable. The changes are only temporary to allow
Windows/MSVC CI pipeline to be established.
Warnings will be made clean in a future series and avoidance of STDC
atomics check will be removed when the publicly available compiler is
formally released.
With this series applied you can do the following from a
"Developer Command Prompt for VS 2022 Preview" with
Visual Studio 17.8.0 Preview 3.0 installed.
meson setup --werror -Denable_stdatomic=true b
meson compile -C b
Tyler Retzlaff (2):
build: temporarily disable MSVC warnings
eal: temporarily disable standard c atomics support for MSVC
config/meson.build | 3 +++
lib/eal/include/rte_stdatomic.h | 2 ++
2 files changed, 5 insertions(+)
--
1.8.3.1
next reply other threads:[~2023-10-17 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 13:13 Tyler Retzlaff [this message]
2023-10-17 13:13 ` [PATCH 1/2] build: temporarily disable MSVC warnings Tyler Retzlaff
2023-10-17 13:31 ` Bruce Richardson
2023-10-17 13:13 ` [PATCH 2/2] eal: temporarily disable standard c atomics support for MSVC Tyler Retzlaff
2023-10-17 13:49 ` [PATCH v2 0/2] make dpdk buildable with latest msvc Tyler Retzlaff
2023-10-17 13:49 ` [PATCH v2 1/2] build: temporarily disable MSVC warnings Tyler Retzlaff
2023-10-17 13:49 ` [PATCH v2 2/2] eal: disable standard c atomics support check for MSVC Tyler Retzlaff
2023-10-31 18:39 ` [PATCH v2 0/2] make dpdk buildable with latest msvc David Marchand
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=1697548427-10153-1-git-send-email-roretzla@linux.microsoft.com \
--to=roretzla@linux.microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.