From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Nick Connolly <nick.connolly@mayadata.io>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>,
dev@dpdk.org, navasile@linux.microsoft.com,
dmitrym@microsoft.com, pallavi.kadam@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] build: fix symlink of drivers for Windows
Date: Sun, 4 Apr 2021 03:00:03 +0300 [thread overview]
Message-ID: <20210404030003.54bf9565@sovereign> (raw)
In-Reply-To: <20210401122723.23082-1-nick.connolly@mayadata.io>
2021-04-01 13:27 (UTC+0100), Nick Connolly:
[...]
> +def copy_pmd_files(pattern, to_dir):
> + for file in glob.glob(os.path.join(pmd_dir, pattern)):
> + to = os.path.join(to_dir, os.path.basename(file))
> + shutil.copy2(file, to)
> + print(to + ' -> ' + file)
> +
> +copy_pmd_files('*rte_*.dll', bin_dir)
> +copy_pmd_files('*rte_*.pdb', bin_dir)
PDB (debuginfo) files can be quite large, do we want to install them?
[...]
> diff --git a/config/meson.build b/config/meson.build
> index 66a2edcc4..c51669b7d 100644
> --- a/config/meson.build
> +++ b/config/meson.build
> @@ -57,11 +57,8 @@ eal_pmd_path = join_paths(get_option('prefix'), driver_install_path)
> # driver .so files often depend upon the bus drivers for their connect bus,
> # e.g. ixgbe depends on librte_bus_pci. This means that the bus drivers need
> # to be in the library path, so symlink the drivers from the main lib directory.
> -if not is_windows
> - meson.add_install_script('../buildtools/symlink-drivers-solibs.sh',
> - get_option('libdir'),
> - pmd_subdir_opt)
> -endif
> +meson.add_install_script(py3, '../buildtools/symlink-drivers-solibs.py',
> + get_option('libdir'), pmd_subdir_opt, get_option('bindir'))
>
> # set the machine type and cflags for it
> if meson.is_cross_build()
As you may have seen, build fails because find_program() result cannot be
used in meson.add_install_script() until 0.55. Since your script has
Unix-specific part anyway and Windows recommends Meson 0.56, maybe Unices
should continue using shell variant and Python script can be Windows-only.
next prev parent reply other threads:[~2021-04-04 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 12:27 Nick Connolly
2021-04-04 0:00 ` Dmitry Kozlyuk [this message]
2021-04-06 10:24 ` Nick Connolly
2021-04-10 8:01 ` [dpdk-stable] [PATCH v2] " Nick Connolly
2021-04-24 0:53 ` Narcisa Ana Maria Vasile
2021-04-26 10:07 ` [dpdk-stable] [PATCH v3] " Nick Connolly
2021-05-27 17:37 ` Nick Connolly
2021-05-28 8:19 ` Bruce Richardson
2021-05-28 10:50 ` Nick Connolly
2021-05-28 8:19 ` Bruce Richardson
2021-07-09 15:05 ` 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=20210404030003.54bf9565@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=nick.connolly@mayadata.io \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=stable@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).