DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/2] doc: enhanced build instructions on Windows
Date: Sun, 27 Oct 2024 00:03:18 +0300	[thread overview]
Message-ID: <20241027000318.6898e3c9@sovereign> (raw)
In-Reply-To: <1729884659-2480-2-git-send-email-andremue@linux.microsoft.com>

2024-10-25 12:30 (UTC-0700), Andre Muezerie:
> -Open a 'Developer PowerShell for VS 2022' prompt from the start menu.
> +Open a 'Visual Studio Developer Command Prompt'. When doing so, it's recommended
> +to specify the Target Architecture (-arch) and the Host Architecture (-host_arch).

It seems that Microsoft documentation [1] uses "target" and "host" terms
for what Meson documentation [2] calls "host" and "build" respectively.
This deserves a notice to avoid confusion.

[1]: https://learn.microsoft.com/en-us/visualstudio/ide/reference/command-prompt-powershell?view=vs-2022
[2]: https://mesonbuild.com/Cross-compilation.html

Why manually specifying architectures is recommended?
If it is mandatory, please use imperative so that no one skips this step.
However, Meson has cross-compilation features, don't they work
(cross-compilation from Windows has never been considered yet)?

>  The developer prompt will configure the environment
>  to select the appropriate compiler, linker and SDK paths
>  required to build with Visual Studio 2022.
>  
>  .. code-block:: console
>  
> +    "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" -host_arch=amd64 -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


  reply	other threads:[~2024-10-26 21:03 UTC|newest]

Thread overview: 19+ 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 [this message]
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
2024-10-31  3:08                   ` [PATCH v5] " Andre Muezerie
2024-11-11 14:11                     ` Thomas Monjalon
2024-11-11 15:59                       ` Andre Muezerie
2024-10-25 19:30       ` [PATCH v2 2/2] doc: provide Meson version that works Andre Muezerie
2024-10-26 20:45         ` Dmitry Kozlyuk
2024-11-11 16:14   ` [PATCH v6] doc: modernize build instructions on Windows Andre Muezerie
2024-11-11 18:18     ` Thomas Monjalon
2024-11-12  9:56     ` Dmitry Kozlyuk
2024-11-19  9:19       ` Thomas Monjalon

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=20241027000318.6898e3c9@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=andremue@linux.microsoft.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 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).