218c4e68c1
Rather than using linuxapp and bsdapp everywhere, we can change things to use the, more readable, terms "linux" and "freebsd" in our build configs. Rather than renaming the configs we can just duplicate the existing ones with the new names using symlinks, and use the new names exclusively internally. ["make showconfigs" also only shows the new names to keep the list short] The result is that backward compatibility is kept fully but any new builds or development can be done using the newer names, i.e. both "make config T=x86_64-native-linuxapp-gcc" and "T=x86_64-native-linux-gcc" work. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
35 lines
842 B
ReStructuredText
35 lines
842 B
ReStructuredText
.. SPDX-License-Identifier: BSD-3-Clause
|
|
Copyright(c) 2010-2014 Intel Corporation.
|
|
|
|
Compiling the Application
|
|
=========================
|
|
|
|
The ``testpmd`` application is compiled as part of the main compilation of the DPDK libraries and tools.
|
|
Refer to the DPDK Getting Started Guides for details.
|
|
The basic compilation steps are:
|
|
|
|
#. Set the required environmental variables and go to the source directory:
|
|
|
|
.. code-block:: console
|
|
|
|
export RTE_SDK=/path/to/rte_sdk
|
|
cd $RTE_SDK
|
|
|
|
#. Set the compilation target. For example:
|
|
|
|
.. code-block:: console
|
|
|
|
export RTE_TARGET=x86_64-native-linux-gcc
|
|
|
|
#. Build the application:
|
|
|
|
.. code-block:: console
|
|
|
|
make install T=$RTE_TARGET
|
|
|
|
The compiled application will be located at:
|
|
|
|
.. code-block:: console
|
|
|
|
$RTE_SDK/$RTE_TARGET/app/testpmd
|