From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: William Tu <u9012063@gmail.com>
Cc: Jeremy Plsek <jplsek@iol.unh.edu>, dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK Windows Build
Date: Tue, 4 Feb 2020 02:02:58 +0300 [thread overview]
Message-ID: <20200204020258.089cc360@Sovereign> (raw)
In-Reply-To: <CALDO+SYcYbXNxRsOanAETOkw=X_8CtCYLX7TJtN35yo_QeSc1w@mail.gmail.com>
> From the step in
> https://mesonbuild.com/Quick-guide.html#installation-from-source
> I tried to compile meson by doing:
> $ git clone https://github.com/mesonbuild/meson.git
> $ cd meson
> $ meson builddir
> ERROR: Neither directory contains a build file meson.build.
>
> How do I generate a meson.build file?
I build Meson from Windows command line (not Git Bash) as pip package:
C:\src\meson> python setup.py install --user
You need write permissions for C:\Python, so use elevated command prompt or
an administrator account. To use the new version, make sure C:\Python\Scripts
is in the beginning of your PATH (assuming C:\Python being your Python 3
installation directory).
Don't forget to apply the patch, it's not in upstream yet. You can instead
clone the fork directly:
git clone -b msvc-linker-arg-prefix https://github.com/PlushBeaver/meson.git
--
Dmitry Kozlyuk
next prev parent reply other threads:[~2020-02-03 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 18:05 Jeremy Plsek
[not found] ` <CALDO+SbTP6jsAsPyupHsXy2+qJLg5ndu31GLniQJN84=be2bNg@mail.gmail.com>
2020-02-01 11:43 ` Dmitry Kozliuk
2020-02-03 19:26 ` William Tu
2020-02-03 22:08 ` Dmitry Kozlyuk
2020-02-03 22:25 ` William Tu
2020-02-03 23:02 ` Dmitry Kozlyuk [this message]
2020-02-03 23:26 ` William Tu
2020-02-03 23:43 ` Dmitry Kozliuk
2020-02-04 0:55 ` William Tu
2020-02-04 6:16 ` Dmitry Kozlyuk
2020-02-04 20:58 ` William Tu
2020-02-04 21:51 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2020-01-28 16:42 Jeremy Plsek
2020-01-28 21:36 ` Dmitry Kozliuk
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=20200204020258.089cc360@Sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=jplsek@iol.unh.edu \
--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 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).