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 2/4] buildtools: use macro to embed information in binaries
Date: Tue, 15 Apr 2025 10:44:51 +0300	[thread overview]
Message-ID: <b005ba52-afc4-4397-a754-f31c3ecdb33a@gmail.com> (raw)
In-Reply-To: <1744680096-17683-3-git-send-email-andremue@linux.microsoft.com>

On 15.04.2025 04:21, Andre Muezerie wrote:
> -_, tmp_root, ar, archive, output, *pmdinfogen = sys.argv
> +_, tmp_root, archiver, archive, output, *pmdinfogen = sys.argv
>   with tempfile.TemporaryDirectory(dir=tmp_root) as temp:
>       paths = []
> -    for name in subprocess.run([ar, "t", archive], stdout=subprocess.PIPE,
> +    if archiver == 'lib':
> +        archiver_options = ['/LIST', '/NOLOGO']
> +    else:
> +        archiver_options = ['t']
> +    for name in subprocess.run([archiver] + archiver_options + [archive], stdout=subprocess.PIPE,
>                                  check=True).stdout.decode().splitlines():
>           if os.path.exists(name):
>               paths.append(name)
>           else:
> -            subprocess.run([ar, "x", os.path.abspath(archive), name],
> +            subprocess.run([archiver, "x", os.path.abspath(archive), name],
>                              check=True, cwd=temp)
>               paths.append(os.path.join(temp, name))
>       subprocess.run(pmdinfogen + paths + [output], check=True)
Does `lib.exe` support `x`? Can't find this option in the doc:
https://learn.microsoft.com/en-us/cpp/build/reference/running-lib?view=msvc-170 


  reply	other threads:[~2025-04-15  7:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 19:39 [PATCH 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-11 19:39 ` [PATCH 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-11 19:39 ` [PATCH 2/4] buildtools: use " Andre Muezerie
2025-04-11 20:07   ` Dmitry Kozlyuk
2025-04-11 19:39 ` [PATCH 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-11 20:09   ` Dmitry Kozlyuk
2025-04-11 19:39 ` [PATCH 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-04-15  1:21 ` [PATCH v2 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-15  1:21   ` [PATCH v2 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-15  1:21   ` [PATCH v2 2/4] buildtools: use " Andre Muezerie
2025-04-15  7:44     ` Dmitry Kozlyuk [this message]
2025-04-15 14:36       ` Andre Muezerie
2025-04-15  1:21   ` [PATCH v2 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-15 11:19     ` Robin Jarry
2025-04-15  1:21   ` [PATCH v2 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-04-16  0:05     ` Stephen Hemminger
2025-04-17 17:10       ` Andre Muezerie
2025-04-15 22:31 ` [PATCH v3 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-15 22:31   ` [PATCH v3 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-15 22:31   ` [PATCH v3 2/4] buildtools: use " Andre Muezerie
2025-04-15 22:31   ` [PATCH v3 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-15 22:31   ` [PATCH v3 4/4] drivers: use macro to embed information in binaries Andre Muezerie
2025-04-16 21:44 ` [PATCH v4 0/4] allow pmdinfo to be inserted and parsed using MSVC Andre Muezerie
2025-04-16 21:44   ` [PATCH v4 1/4] eal: add macro to embed information in binaries Andre Muezerie
2025-04-16 21:44   ` [PATCH v4 2/4] buildtools: use " Andre Muezerie
2025-04-16 21:44   ` [PATCH v4 3/4] usertools: parse strings from PE images Andre Muezerie
2025-04-16 21:44   ` [PATCH v4 4/4] drivers: use macro to embed information in binaries Andre Muezerie

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=b005ba52-afc4-4397-a754-f31c3ecdb33a@gmail.com \
    --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).