From: Thomas Monjalon <thomas@monjalon.net>
To: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, heraklusz.lipiec@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: add generic compilation doc for all sample apps
Date: Sun, 09 Jul 2017 23:20:57 +0200 [thread overview]
Message-ID: <3434938.x7so3z7SW3@xps> (raw)
In-Reply-To: <20170629084044.32173-1-herakliusz.lipiec@intel.com>
Hi,
This method is deprecated.
See below for updating the commands.
29/06/2017 10:40, Herakliusz Lipiec:
> +Set the path to DPDK source code if its not set:
> +
> + .. code-block:: console
> +
> + export RTE_SDK=/path/to/rte_sdk
> +
> +Set the target (a default target is used if not specified). For example:
> +
> + .. code-block:: console
> +
> + export RTE_TARGET=x86_64-native-linuxapp-gcc
No need to export RTE_TARGET at this point.
This target is just needed for "make config".
> +Go to DPDK source:
> +
> + .. code-block:: console
> +
> + cd $RTE_SDK
> +
> +Make and install DPDK:
> +
> + .. code-block:: console
> +
> + make install T=$RTE_TARGET
The new standard method is:
make config T=$RTE_TARGET
make
The config can be tuned between these two commands.
The command "make install" is not required to build examples.
> +Build the sample applications:
> +
> + .. code-block:: console
> +
> + make examples T=$RTE_TARGET
You can use this command with the new method:
export RTE_TARGET=build
make -C examples
Note that the target for examples is the DPDK build directory.
It can be different if O= was used when configuring/compiling DPDK.
prev parent reply other threads:[~2017-07-09 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 16:35 [dpdk-dev] [PATCH] " Herakliusz Lipiec
2017-06-14 18:26 ` Mcnamara, John
2017-06-29 8:40 ` [dpdk-dev] [PATCH v2] " Herakliusz Lipiec
2017-06-29 16:33 ` Mcnamara, John
2017-07-09 21:20 ` Thomas Monjalon [this message]
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=3434938.x7so3z7SW3@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=herakliusz.lipiec@intel.com \
--cc=heraklusz.lipiec@intel.com \
--cc=john.mcnamara@intel.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).