[dpdk-dev] [PATCH 2/3] doc: how to build
Olivier MATZ
olivier.matz at 6wind.com
Fri May 17 11:06:11 CEST 2013
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 at 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
More information about the dev
mailing list