apps: add name to LPM parameters

[dpdk.git] / doc / guides / prog_guide / dev_kit_build_system.rst

diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst b/doc/guides/prog_guide/dev_kit_build_system.rst
index 23944f4..dd3e3d0 100644 (file)
--- a/doc/guides/prog_guide/dev_kit_build_system.rst
+++ b/doc/guides/prog_guide/dev_kit_build_system.rst
@@ -85,7 +85,7 @@ Each build directory contains include files, libraries, and applications:
 
     librte_cmdline.a librte_lpm.a librte_mempool.a librte_ring.a
 
-    librte_eal.a librte_malloc.a librte_pmd_e1000.a librte_timer.a
+    librte_eal.a librte_pmd_e1000.a librte_timer.a
 
 
     ~/DEV/DPDK$ ls i686-native-linuxapp-gcc/include/
@@ -194,7 +194,7 @@ To compile an application, the user must set the RTE_SDK and RTE_TARGET environm
     cd /path/to/my_app
 
 For a new application, the user must create their own Makefile that includes some .mk files, such as
-${RTE_SDK}/mk/DPDK.vars.mk, and ${RTE_SDK}/mk/ DPDK.app.mk.
+${RTE_SDK}/mk/rte.vars.mk, and ${RTE_SDK}/mk/ rte.app.mk.
 This is described in
 :ref:`Building Your Own Application <Building_Your_Own_Application>`.
 
@@ -217,11 +217,11 @@ General Rules For DPDK Makefiles
 
 In the DPDK, Makefiles always follow the same scheme:
 
-#. Include $(RTE_SDK)/mk/DPDK.vars.mk at the beginning.
+#. Include $(RTE_SDK)/mk/rte.vars.mk at the beginning.
 
 #. Define specific variables for RTE build system.
 
-#. Include a specific $(RTE_SDK)/mk/DPDK.XYZ.mk, where XYZ can be app, lib, extapp, extlib, obj, gnuconfigure,
+#. Include a specific $(RTE_SDK)/mk/rte.XYZ.mk, where XYZ can be app, lib, extapp, extlib, obj, gnuconfigure,
    and so on, depending on what kind of object you want to build.
    :ref:`See Makefile Types <Makefile_Types>` below.
 
@@ -231,7 +231,7 @@ In the DPDK, Makefiles always follow the same scheme:
 
    ..  code-block:: make
 
-        include $(RTE_SDK)/mk/DPDK.vars.mk
+        include $(RTE_SDK)/mk/rte.vars.mk
 
         # binary name
         APP = helloworld
@@ -242,7 +242,7 @@ In the DPDK, Makefiles always follow the same scheme:
         CFLAGS += -O3
         CFLAGS += $(WERROR_FLAGS)
 
-        include $(RTE_SDK)/mk/DPDK.extapp.mk
+        include $(RTE_SDK)/mk/rte.extapp.mk
 
 .. _Makefile_Types:
 
@@ -317,7 +317,7 @@ Useful Variables Provided by the Build System
     When compiling an external application, the variable points to the root of external application sources.
 
 *   RTE_OUTPUT: The path to which output files are written.
-    Typically, it is $(RTE_SRCDIR)/build, but it can be overriden by the O= option in the make command line.
+    Typically, it is $(RTE_SRCDIR)/build, but it can be overridden by the O= option in the make command line.
 
 *   RTE_TARGET: A string identifying the target for which we are building.
     The format is arch-machine-execenv-toolchain.
@@ -407,12 +407,12 @@ Variables that Can be Set/Overridden by the User in a Makefile or Command Line
 
 *   LDFLAGS_my_app: Specific flags to add when linking my_app.
 
-*   NO_AUTOLIBS: If set, the libraries provided by the framework will not be included in the LDLIBS variable automatically.
-
 *   EXTRA_CFLAGS: The content of this variable is appended after CFLAGS when compiling.
 
 *   EXTRA_LDFLAGS: The content of this variable is appended after LDFLAGS when linking.
 
+*   EXTRA_LDLIBS: The content of this variable is appended after LDLIBS when linking.
+
 *   EXTRA_ASFLAGS: The content of this variable is appended after ASFLAGS when assembling.
 
 *   EXTRA_CPPFLAGS: The content of this variable is appended after CPPFLAGS when using a C preprocessor on assembly files.