d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
d2d7d6fc5f
numam-dpdk/doc/build-sdk-quick.txt

28 lines
1.1 KiB
Plaintext
Raw Normal View History

doc: how to build 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@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2013-05-07 15:00:52 +00:00
Basic build
config: rename "default" configurations as "native" The "default" part in configuration filenames is misleading. Rename this as "native", as this is the RTE_MACHINE that is set in these files. This should make it clearer for people who build DPDK on a system then run it on another one. Signed-off-by: David Marchand <david.marchand@6wind.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2014-05-14 14:58:08 +00:00
make config T=x86_64-native-linuxapp-gcc && make
doc: how to build 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@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2013-05-07 15:00:52 +00:00
Build commands
mk: add "make examples" target in root makefile It is now possible to build all projects from the examples/ directory using one command from root directory. Some illustration of what is possible: - build examples in the DPDK tree for one target # install the x86_64-default-linuxapp-gcc in # ${RTE_SDK}/x86_64-default-linuxapp-gcc directory user@droids:~/dpdk.org$ make install T=x86_64-default-linuxapp-gcc # build examples for this new installation in # ${RTE_SDK}/examples directory user@droids:~/dpdk.org$ make examples T=x86_64-default-linuxapp-gcc - build examples outside DPDK tree for several targets # install all targets matching x86_64-*-linuxapp-gcc in # ${RTE_SDK}/x86_64-*-linuxapp-gcc directories user@droids:~/dpdk.org$ make install T=x86_64-*-linuxapp-gcc # build examples for these installations in /tmp/foobar user@droids:~/dpdk.org$ make examples T=x86_64-*-linuxapp-gcc O=/tmp/foobar Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2014-05-16 08:19:01 +00:00
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
mk: introduce new install syntax The old install command was: make install T=x86_64-native-linuxapp-gcc DESTDIR=install It still works and can be replaced by these more standard commands: make config T=x86_64-native-linuxapp-gcc 0=x86_64-native-linuxapp-gcc make O=x86_64-native-linuxapp-gcc make install O=x86_64-native-linuxapp-gcc prefix= DESTDIR=install It means the "make install" do not perform any compilation anymore when T is not used. It is done only in pre_install to keep compatibility with the old syntax based on T= option. The default prefix /usr/local is empty in the T= case which is used only for a local install. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Panu Matilainen <pmatilai@redhat.com>
2015-12-01 14:04:01 +00:00
install T= configure, build and install a target in DESTDIR
install install optionally staged in DESTDIR
mk: add "make examples" target in root makefile It is now possible to build all projects from the examples/ directory using one command from root directory. Some illustration of what is possible: - build examples in the DPDK tree for one target # install the x86_64-default-linuxapp-gcc in # ${RTE_SDK}/x86_64-default-linuxapp-gcc directory user@droids:~/dpdk.org$ make install T=x86_64-default-linuxapp-gcc # build examples for this new installation in # ${RTE_SDK}/examples directory user@droids:~/dpdk.org$ make examples T=x86_64-default-linuxapp-gcc - build examples outside DPDK tree for several targets # install all targets matching x86_64-*-linuxapp-gcc in # ${RTE_SDK}/x86_64-*-linuxapp-gcc directories user@droids:~/dpdk.org$ make install T=x86_64-*-linuxapp-gcc # build examples for these installations in /tmp/foobar user@droids:~/dpdk.org$ make examples T=x86_64-*-linuxapp-gcc O=/tmp/foobar Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2014-05-16 08:19:01 +00:00
examples build examples for given targets (T=)
examples_clean clean examples for given targets (T=)
doc: how to build 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@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2013-05-07 15:00:52 +00:00
Build variables
EXTRA_CPPFLAGS preprocessor options
EXTRA_CFLAGS compiler options
EXTRA_LDFLAGS linker options
mk: introduce EXTRA_LDLIBS variable Signed-off-by: Keith Wiles <keith.wiles@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2015-05-14 14:21:32 +00:00
EXTRA_LDLIBS linker library options
doc: how to build 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@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2013-05-07 15:00:52 +00:00
RTE_KERNELDIR linux headers path
mk: stop on warning only in developer build Add RTE_DEVEL_BUILD make-variable which can be used to do things differently when doing development vs building a release, autodetected from source root .git presence and overridable via commandline. It is used it to enable -Werror compiler flag and may be extended to other checks. Failing build on warnings is a useful developer tool but its bad for release tarballs which can and do get built with newer compilers than what was used/available during development. Compilers routinely add new warnings so code which built silently with cc X might no longer do so with X+1. This doesn't make the existing code any more buggier and failing the build in this case does not help to improve the quality of an already released version either. This change the default flags which can be tuned with EXTRA_CFLAGS. Signed-off-by: Panu Matilainen <pmatilai@redhat.com> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2015-02-12 15:18:20 +00:00
RTE_DEVEL_BUILD stricter options (default: y in git tree)
mk: allow to specify DESTDIR in build rule This will install the binary sdk (bin + modules + libs + headers + mk) in the specified directory. This directory can be used as RTE_SDK by external applications. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2013-01-30 15:32:15 +00:00
CROSS toolchain prefix
V verbose
D debug dependencies
mk: introduce new install syntax The old install command was: make install T=x86_64-native-linuxapp-gcc DESTDIR=install It still works and can be replaced by these more standard commands: make config T=x86_64-native-linuxapp-gcc 0=x86_64-native-linuxapp-gcc make O=x86_64-native-linuxapp-gcc make install O=x86_64-native-linuxapp-gcc prefix= DESTDIR=install It means the "make install" do not perform any compilation anymore when T is not used. It is done only in pre_install to keep compatibility with the old syntax based on T= option. The default prefix /usr/local is empty in the T= case which is used only for a local install. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Panu Matilainen <pmatilai@redhat.com>
2015-12-01 14:04:01 +00:00
O build directory (default: build/ - install T= default: ./)
DESTDIR staging install directory
mk: install a standard cutomizable tree The rule "install" follows these conventions: http://gnu.org/prep/standards/html_node/Directory-Variables.html http://gnu.org/prep/standards/html_node/DESTDIR.html The variable sdkdir has been added to the more standards ones, to configure the directory used with RTE_SDK when using the DPDK makefiles to build an application. It is still possible to build DPDK with the "install T=" rule without specifying any DESTDIR. In such case there is no install, as before. The old usage of an installed SDK is: make -C examples/helloworld RTE_SDK=$(readlink -m $DESTDIR) \ RTE_TARGET=x86_64-native-linuxapp-gcc RTE_TARGET can be specified but is useless now with an installed SDK. The RTE_SDK directory must now point to a different path depending of the installation. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Panu Matilainen <pmatilai@redhat.com>
2015-12-01 11:47:48 +00:00
prefix root install directory
mk: remove multi-target install The multi-target install create some subdirectories with the target name which is not standard for a "make install" procedure. The uninstall procedure cannot be applied properly (without removing all files in a directory). It would need to pre-compute paths. As it is a packaging issue, it is removed from the build system capabilities. The variable BUILD_DIR is also renamed to RTE_OUTPUT used in other files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Panu Matilainen <pmatilai@redhat.com>
2015-12-01 07:36:00 +00:00
T target template - used with config or install
doc: how to build 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@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2013-05-07 15:00:52 +00:00
format: <arch-machine-execenv-toolchain>
templates in config/defconfig_*
Reference in New Issue Copy Permalink