From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Sergey Madaminov <sergey.madaminov@gmail.com>
Cc: William Tu <u9012063@gmail.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK meson build failed on Windows
Date: Wed, 4 Aug 2021 23:19:19 +0300 [thread overview]
Message-ID: <20210804231919.32bc6e98@sovereign> (raw)
In-Reply-To: <CAAFdL+=RBHELtWZh04rD5uBm9V2vBY3gAJWok9JPt6G2sayHyA@mail.gmail.com>
2021-08-04 14:28 (UTC-0500), Sergey Madaminov:
> I've taken a look at this issue. As Dmitry said it is related to the bug
> within meson with having slashes escaping characters. It matters for the
> current meson build files in the DPDK for Windows as there is a reliance on
> strings for some file names.
What do you mean? "librte_kvargs.lib" from the error message should be
"lib\rte_kvargs.lib" because "rte_kvargs.lib" is produced inside "lib"
directory. It is pure meson error in generating ninja commands.
> I believe that it is solvable by replacing
> strings and transitioning to variables. So if there is an interest in that
> or a need to use higher versions of meson I can try to rewrite meson build
> files to solve this problem. Chances I may do that anyway as for current
> OvS meson builds I need meson 0.59.0 version.
DPDK meson.build files must stay compatible with meson 0.49.2.
next prev parent reply other threads:[~2021-08-04 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 18:31 [dpdk-dev] DPDK meson build failed on Windows William Tu
2021-08-04 18:45 ` Dmitry Kozlyuk
2021-08-04 19:28 ` Sergey Madaminov
2021-08-04 20:19 ` Dmitry Kozlyuk [this message]
2021-08-04 22:14 ` Sergey Madaminov
2021-08-05 13:00 ` William Tu
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=20210804231919.32bc6e98@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=sergey.madaminov@gmail.com \
--cc=u9012063@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.