From: Luca Boccassi <bluca@debian.org>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] build: mention machine=default and its use in documentation
Date: Wed, 27 Feb 2019 12:16:11 +0000 [thread overview]
Message-ID: <913c24a1beca6c41b9ba24641fa151fc76c21c36.camel@debian.org> (raw)
In-Reply-To: <20190114134106.17383-1-bluca@debian.org>
On Mon, 2019-01-14 at 13:41 +0000, Luca Boccassi wrote:
> Document the new value, as it's useful for distributions and users
> who need to use a stable baseline -march
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> Reviewed-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> v2: fix typo, add commit body and reviewed-by
>
> doc/build-sdk-meson.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/build-sdk-meson.txt b/doc/build-sdk-meson.txt
> index 29a8bd387..ab33ca82a 100644
> --- a/doc/build-sdk-meson.txt
> +++ b/doc/build-sdk-meson.txt
> @@ -87,6 +87,8 @@ Project-specific options are passed used
> -Doption=value::
>
> meson -Denable_docs=true fullbuild # build and install docs
>
> + meson -Dmachine=default # use builder-independent baseline
> -march
> +
> Examples of setting the same options using meson configure::
>
> meson configure -Dwerror=true
> @@ -103,6 +105,9 @@ should be used to change the build settings
> within the directory, and when
> ``ninja`` is called to do the build itself, it will trigger the
> necessary
> re-scan from meson.
>
> +NOTE: machine=default will use the minimum required -march on all
> architectures
> +regardless of the capabilities of the machine where the build is
> happening.
> +
> As well as those settings taken from ``meson configure``, other
> options
> such as the compiler to use can be passed via environment variables.
> For
> example::
Ping - anything else I can do for this patch? Thanks!
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-02-27 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 11:23 [dpdk-dev] [PATCH] " Luca Boccassi
2019-01-14 13:32 ` Christian Ehrhardt
2019-01-14 13:44 ` Luca Boccassi
2019-01-14 13:41 ` [dpdk-dev] [PATCH v2] " Luca Boccassi
2019-02-27 12:16 ` Luca Boccassi [this message]
2019-03-18 20:12 ` Jerin Jacob Kollanukkaran
2019-03-18 20:12 ` Jerin Jacob Kollanukkaran
2019-04-17 20:17 ` Thomas Monjalon
2019-04-17 20:17 ` Thomas Monjalon
2019-04-18 9:30 ` Luca Boccassi
2019-04-18 9:30 ` Luca Boccassi
2019-04-18 9:30 ` [dpdk-dev] [PATCH v3] " luca.boccassi
2019-04-18 9:30 ` luca.boccassi
2019-04-18 14:06 ` Thomas Monjalon
2019-04-18 14:06 ` 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=913c24a1beca6c41b9ba24641fa151fc76c21c36.camel@debian.org \
--to=bluca@debian.org \
--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).