From: Olivier MATZ <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/3] doc: how to build
Date: Fri, 17 May 2013 11:06:11 +0200 [thread overview]
Message-ID: <5195F303.2080004@6wind.com> (raw)
In-Reply-To: <fa5bbf77e53cbef7f33b49b1e8b01e960d0ce4c1.1367939814.git.thomas.monjalon@6wind.com>
Hi Thomas,
Good to see a "make help" ;)
What do you think of replacing "Build options" by "Build variables" ?
I think it is not obvious that we have to use V=1 for instance for
a verbose build.
About the "build targets", I suggest to include it in the help of T
variable. What do you think ?
Olivier
On 05/07/2013 05:17 PM, Thomas Monjalon wrote:
> This is a cheat sheet to build DPDK and can be used for a "make help".
> It is explicitly described as a build help in order to concatenate it
> with other helps such as test commands.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> doc/build-sdk-quick.txt | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 doc/build-sdk-quick.txt
>
> diff --git a/doc/build-sdk-quick.txt b/doc/build-sdk-quick.txt
> new file mode 100644
> index 0000000..3f88522
> --- /dev/null
> +++ b/doc/build-sdk-quick.txt
> @@ -0,0 +1,22 @@
> +Basic build
> + make config T=x86_64-default-linuxapp-gcc && make
> +Build commands
> + config get configuration from target template (T=)
> + all same as build (default rule)
> + build build in a configured directory
> + clean remove files but keep configuration
> + install build many targets (wildcard allowed) in fixed directories
> + uninstall remove all installed targets
> +Build options
> + T target template (install default: *) - used with config or install
> + O output directory (default: build/) - cannot be used with install
> + V verbose
> + D debug dependencies
> + CROSS toolchain prefix
> + EXTRA_CPPFLAGS preprocessor options
> + EXTRA_CFLAGS compiler options
> + EXTRA_LDFLAGS linker options
> +Build targets
> + format: <arch-machine-execenv-toolchain>
> + templates in config/defconfig_*:
> + # make showconfigs
next prev parent reply other threads:[~2013-05-17 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 15:17 [dpdk-dev] [PATCH 0/3] make help Thomas Monjalon
2013-05-07 15:17 ` [dpdk-dev] [PATCH 1/3] mk: rule showconfigs for configs listing Thomas Monjalon
2013-05-17 9:05 ` Olivier MATZ
2013-05-17 14:53 ` Thomas Monjalon
2013-05-07 15:17 ` [dpdk-dev] [PATCH 2/3] doc: how to build Thomas Monjalon
2013-05-17 9:06 ` Olivier MATZ [this message]
2013-05-17 15:20 ` Thomas Monjalon
2013-05-07 15:17 ` [dpdk-dev] [PATCH 3/3] mk: rule help Thomas Monjalon
2013-05-17 9:06 ` Olivier MATZ
2013-05-17 15:27 ` Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 0/3] make help Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 1/3] doc: how to build Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 2/3] mk: rule showconfigs for configs listing Thomas Monjalon
2013-05-28 22:15 ` [dpdk-dev] [PATCH v2 3/3] mk: rule help Thomas Monjalon
2013-05-30 14:55 ` [dpdk-dev] [PATCH v2 0/3] make help Olivier MATZ
2013-05-30 22:02 ` 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=5195F303.2080004@6wind.com \
--to=olivier.matz@6wind.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).