net/memif: optimize with one-way barrier

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

diff --git a/doc/guides/prog_guide/build_app.rst b/doc/guides/prog_guide/build_app.rst
index d28d735..bffa55b 100644 (file)
--- a/doc/guides/prog_guide/build_app.rst
+++ b/doc/guides/prog_guide/build_app.rst
@@ -1,32 +1,5 @@
-..  BSD LICENSE
-    Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
-    All rights reserved.
-
-    Redistribution and use in source and binary forms, with or without
-    modification, are permitted provided that the following conditions
-    are met:
-
-    * Redistributions of source code must retain the above copyright
-    notice, this list of conditions and the following disclaimer.
-    * Redistributions in binary form must reproduce the above copyright
-    notice, this list of conditions and the following disclaimer in
-    the documentation and/or other materials provided with the
-    distribution.
-    * Neither the name of Intel Corporation nor the names of its
-    contributors may be used to endorse or promote products derived
-    from this software without specific prior written permission.
-
-    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+..  SPDX-License-Identifier: BSD-3-Clause
+    Copyright(c) 2010-2014 Intel Corporation.

 
 .. _Building_Your_Own_Application:
 
 
 .. _Building_Your_Own_Application:
 


@@ -43,7 +16,7 @@ RTE_SDK and RTE_TARGET.
 
     ~/DPDK$ cd examples/helloworld/
     ~/DPDK/examples/helloworld$ export RTE_SDK=/home/user/DPDK
 
     ~/DPDK$ cd examples/helloworld/
     ~/DPDK/examples/helloworld$ export RTE_SDK=/home/user/DPDK

-    ~/DPDK/examples/helloworld$ export RTE_TARGET=x86_64-native-linuxapp-gcc
+    ~/DPDK/examples/helloworld$ export RTE_TARGET=x86_64-native-linux-gcc

     ~/DPDK/examples/helloworld$ make
         CC main.o
         LD helloworld
     ~/DPDK/examples/helloworld$ make
         CC main.o
         LD helloworld


@@ -67,7 +40,7 @@ The sample application (Hello World) can be duplicated in a new directory as a s
     ~$ cp -r DPDK/examples/helloworld my_rte_app
     ~$ cd my_rte_app/
     ~/my_rte_app$ export RTE_SDK=/home/user/DPDK
     ~$ cp -r DPDK/examples/helloworld my_rte_app
     ~$ cd my_rte_app/
     ~/my_rte_app$ export RTE_SDK=/home/user/DPDK

-    ~/my_rte_app$ export RTE_TARGET=x86_64-native-linuxapp-gcc
+    ~/my_rte_app$ export RTE_TARGET=x86_64-native-linux-gcc

     ~/my_rte_app$ make
         CC main.o
         LD helloworld
     ~/my_rte_app$ make
         CC main.o
         LD helloworld


@@ -82,9 +55,9 @@ Application Makefile
 
 The default makefile provided with the Hello World sample application is a good starting point. It includes:
 
 
 The default makefile provided with the Hello World sample application is a good starting point. It includes:
 

-*   $(RTE_SDK)/mk/DPDK.vars.mk at the beginning
+*   $(RTE_SDK)/mk/rte.vars.mk at the beginning

 
 

-*   $(RTE_SDK)/mk/DPDK.extapp.mk at the end
+*   $(RTE_SDK)/mk/rte.extapp.mk at the end

 
 The user must define several variables:
 
 
 The user must define several variables:
 


@@ -97,9 +70,9 @@ Library Makefile
 
 It is also possible to build a library in the same way:
 
 
 It is also possible to build a library in the same way:
 

-*   Include $(RTE_SDK)/mk/DPDK.vars.mk at the beginning.
+*   Include $(RTE_SDK)/mk/rte.vars.mk at the beginning.

 
 

-*   Include $(RTE_SDK)/mk/DPDK.extlib.mk  at the end.
+*   Include $(RTE_SDK)/mk/rte.extlib.mk  at the end.

 
 The only difference is that APP should be replaced by LIB, which contains the name of the library. For example, libfoo.a.
 
 
 The only difference is that APP should be replaced by LIB, which contains the name of the library. For example, libfoo.a.
 


@@ -124,5 +97,3 @@ chapter for details.
 *   CPPFLAGS: The flags to use to provide flags to the C preprocessor (only useful when assembling .S files)
 
 *   LDLIBS: A list of libraries to link with (for example, -L /path/to/libfoo - lfoo)
 *   CPPFLAGS: The flags to use to provide flags to the C preprocessor (only useful when assembling .S files)
 
 *   LDLIBS: A list of libraries to link with (for example, -L /path/to/libfoo - lfoo)

-
-*   NO_AUTOLIBS: If set, the libraries provided by the framework will not be included in the LDLIBS variable automatically.