DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: bruce.richardson@intel.com, dev@dpdk.org, vladimir.medvedkin@intel.com
Subject: [PATCH v2 2/2] lib/lpm: enable lpm to be compiled with MSVC
Date: Fri, 16 May 2025 10:36:42 -0700	[thread overview]
Message-ID: <1747417002-28419-3-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1747417002-28419-1-git-send-email-andremue@linux.microsoft.com>

Now that all issues related to lpm are addressed it can be enabled
for MSVC.

Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
---
 lib/lpm/meson.build | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/lib/lpm/meson.build b/lib/lpm/meson.build
index fae4f79fb9..cff8fed473 100644
--- a/lib/lpm/meson.build
+++ b/lib/lpm/meson.build
@@ -1,12 +1,6 @@
 # SPDX-License-Identifier: BSD-3-Clause
 # Copyright(c) 2017 Intel Corporation
 
-if is_ms_compiler
-    build = false
-    reason = 'not supported building with Visual Studio Toolset'
-    subdir_done()
-endif
-
 sources = files('rte_lpm.c', 'rte_lpm6.c')
 headers = files('rte_lpm.h', 'rte_lpm6.h')
 # since header files have different names, we can install all vector headers
-- 
2.49.0.vfs.0.3


      parent reply	other threads:[~2025-05-16 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  2:20 [PATCH] lib/lpm: use standard atomic_store_explicit Andre Muezerie
2024-12-04  7:56 ` David Marchand
2024-12-04 16:20   ` Andre Muezerie
2024-12-04 16:52     ` Bruce Richardson
2024-12-04 19:09       ` Andre Muezerie
2025-05-16 17:36 ` [PATCH v2 0/2] enable lpm to be compiled with MSVC Andre Muezerie
2025-05-16 17:36   ` [PATCH v2 1/2] lib/lpm: use standard atomic_store_explicit Andre Muezerie
2025-05-16 17:36   ` Andre Muezerie [this message]

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=1747417002-28419-3-git-send-email-andremue@linux.microsoft.com \
    --to=andremue@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=vladimir.medvedkin@intel.com \
    /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).