From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1205745C1A; Thu, 31 Oct 2024 04:08:58 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D496440273; Thu, 31 Oct 2024 04:08:57 +0100 (CET) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id 2EA7D400EF for ; Thu, 31 Oct 2024 04:08:55 +0100 (CET) Received: by linux.microsoft.com (Postfix, from userid 1213) id 742422054B70; Wed, 30 Oct 2024 20:08:54 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 742422054B70 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1730344134; bh=FzSFsjBxsczl1tFPv3EiC0DkIlH3gyO/KCcbHKFL1rY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=NPrMvq2r+rF1aogUyvuC6QmL4Lgc9oqATdMb3zQ6T1G8jDMVY+OVsGJNiYbds5rki 8NypXlOzlJwQepcEHx31UOM7C8Hd2sBaKc+5iKi4WRentwSNTI+rKbZZVhL0FirPW7 bUbiVPNy6ifZhVjdIaSrhUieLen26NGZhDcR+ehQ= From: Andre Muezerie To: stephen@networkplumber.org Cc: andremue@linux.microsoft.com, dev@dpdk.org, dmitry.kozliuk@gmail.com Subject: [PATCH v5] doc: modernize build instructions on Windows Date: Wed, 30 Oct 2024 20:08:40 -0700 Message-Id: <1730344120-13937-1-git-send-email-andremue@linux.microsoft.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <20241030084854.5630a336@hermes.local> References: <20241030084854.5630a336@hermes.local> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Meson 0.57 was an unstable version and is now outdated. The referenced bug in Meson 0.58 is fixed in stable releases. Recommend the latest stable release which is tested. Building DPDK applications that run on 32-bit Windows is currently not supported. However, some Visual Studio environments default to producing 32-bit binaries. Recommend instructing the developer prompt to produce 64-bit binaries when that is the case. Signed-off-by: Andre Muezerie --- v5: - Added new line at end of file build_dpdk.rst v4: - Clarified that "32-bit binaries" was refering to the Windows environment. - Added clarifying commit messages. v3: - Recommended Meson version to use and removed mention about old bug. - Set VS developer prompt to produce 64 bit binaries if needed. v2: - provide Meson version that works .mailmap | 1 + doc/guides/windows_gsg/build_dpdk.rst | 20 +++++++++++++++----- 2 files changed, 16 insertions(+), 5 deletions(-) diff --git a/.mailmap b/.mailmap index 5290420..60db768 100644 --- a/.mailmap +++ b/.mailmap @@ -98,6 +98,7 @@ Anatolii Gerasymenko Anatoly Burakov Anbarasan Murugesan Anders Roxell +Andre Muezerie Andrea Arcangeli Andrea Grandi Andre Richter diff --git a/doc/guides/windows_gsg/build_dpdk.rst b/doc/guides/windows_gsg/build_dpdk.rst index 708875c..cac6725 100644 --- a/doc/guides/windows_gsg/build_dpdk.rst +++ b/doc/guides/windows_gsg/build_dpdk.rst @@ -72,10 +72,7 @@ A good option to choose is the MSI installer for both meson and ninja together:: http://mesonbuild.com/Getting-meson.html#installing-meson-and-ninja-with-the-msi-installer%22 -Required version is Meson 0.57. - -Versions starting from 0.58 are unusable with LLVM toolchain -because of a `Meson issue `_. +Meson version 1.5.2 or newer is recommended. Install the Backend @@ -129,11 +126,24 @@ Depending on the distribution, paths in this file may need adjustments. Option 3. Native Build on Windows using MSVC ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Open a 'Developer PowerShell for VS 2022' prompt from the start menu. +Open a 'Visual Studio Developer Command Prompt'. The developer prompt will configure the environment to select the appropriate compiler, linker and SDK paths required to build with Visual Studio 2022. +Building DPDK applications that run on 32-bit Windows is currently not +supported. If your Visual Studio environment defaults to producing +32-bit binaries you can instruct the toolset to produce 64-bit binaries using "-arch" parameter. +For more details about the Developer Prompt options look at the `Visual Studio Developer +Command Prompt and Developer PowerShell +`_. + +.. code-block:: console + + "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" -arch=amd64 + +Compile the code from the developer prompt. + .. code-block:: console cd C:\Users\me\dpdk -- 1.8.3.1