DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dmitry.kozliuk@gmail.com, dev@dpdk.org
Subject: Re: [PATCH v4] doc: modernize build instructions on Windows
Date: Wed, 30 Oct 2024 08:48:54 -0700	[thread overview]
Message-ID: <20241030084854.5630a336@hermes.local> (raw)
In-Reply-To: <1730301585-14536-1-git-send-email-andremue@linux.microsoft.com>

On Wed, 30 Oct 2024 08:19:45 -0700
Andre Muezerie <andremue@linux.microsoft.com> wrote:

> 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 <andremue@linux.microsoft.com>
> ---
> v4:
>  - Clarified that "32-bit binaries" were 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 | 22 ++++++++++++++++------
>  2 files changed, 17 insertions(+), 6 deletions(-)
> 
> diff --git a/.mailmap b/.mailmap
> index 5290420..60db768 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -98,6 +98,7 @@ Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
>  Anatoly Burakov <anatoly.burakov@intel.com>
>  Anbarasan Murugesan <anbarasanx.murugesan@intel.com>
>  Anders Roxell <anders.roxell@linaro.org>
> +Andre Muezerie <andremue@linux.microsoft.com> <andremue@microsoft.com>
>  Andrea Arcangeli <aarcange@redhat.com>
>  Andrea Grandi <andrea.grandi@intel.com>
>  Andre Richter <andre.o.richter@gmail.com>
> diff --git a/doc/guides/windows_gsg/build_dpdk.rst b/doc/guides/windows_gsg/build_dpdk.rst
> index 708875c..ff89e95 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 <https://github.com/mesonbuild/meson/issues/8981>`_.
> +Meson version 1.5.2 or newer is recommended.
>  
>  
>  Install the Backend
> @@ -129,13 +126,26 @@ 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
> +<https://learn.microsoft.com/en-us/visualstudio/ide/reference/command-prompt-powershell?view=vs-2022>`_.
> +
> +.. 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
>     meson setup -Denable_stdatomic=true build
> -   meson compile -C build
> +   meson compile -C build
> \ No newline at end of file

Please fix the file to have newline at end.

  reply	other threads:[~2024-10-30 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 14:15 [PATCH] doc: enhance build instructions on windows Andre Muezerie
2024-10-25 14:15 ` [PATCH] doc: enhanced build instructions on Windows Andre Muezerie
2024-10-25 14:50   ` Thomas Monjalon
2024-10-25 19:30     ` [PATCH v2 0/2] doc: enhance build instructions on windows Andre Muezerie
2024-10-25 19:30       ` [PATCH v2 1/2] doc: enhanced build instructions on Windows Andre Muezerie
2024-10-26 21:03         ` Dmitry Kozlyuk
2024-10-28 19:45           ` [PATCH v3] doc: enhance " Andre Muezerie
2024-10-30  9:09             ` Dmitry Kozlyuk
2024-10-30 15:19               ` [PATCH v4] doc: modernize " Andre Muezerie
2024-10-30 15:48                 ` Stephen Hemminger [this message]
2024-10-25 19:30       ` [PATCH v2 2/2] doc: provide Meson version that works Andre Muezerie
2024-10-26 20:45         ` Dmitry Kozlyuk

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=20241030084854.5630a336@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=andremue@linux.microsoft.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.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).