From 388846bb8dd643e65a4c660a13b285229065ae14 Mon Sep 17 00:00:00 2001 From: Daniel Borkmann Date: Thu, 11 Jul 2013 12:20:57 +0200 Subject: docs: install: state that we do have an option for distro build Brind the doc more up to date since we do have DISTRO=1 et al available from the build system. Thus, no manual hand-tweaking needs to be done, only in rare cases if really necessary. Signed-off-by: Daniel Borkmann --- INSTALL | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) (limited to 'INSTALL') diff --git a/INSTALL b/INSTALL index 5bfba1f..f2deb5d 100644 --- a/INSTALL +++ b/INSTALL @@ -70,9 +70,10 @@ In order to remove all build files from the source tree: $ make clean +In any case "make help" will give you some pointers of what can be done. To bring the source tree into a pristine state, there are two options. -The first one will remove all build and build config file, the latter -will also remove any manually added files: +The first one will remove all build and build config file, the latter will +also remove any manually added files: $ make distclean ($ make mrproper) @@ -151,24 +152,26 @@ symbols, do: $ make DEBUG=1 -For debugging the build system, full commands are shown if every make target is -executed with: +For debugging the build system, actual commands are verbosly shown if every +make target is executed with: $ make Q= Concerning packaging the toolkit for a Linux distribution, by default, netsniff-ng has some architecture-specific tuning options enabled that don't -belong into a package binary of a distribution. Hence, you might want to adapt -some build-related things before starting to package the toolkit. All -necessary things (e.g., CFLAGS,WFLAGS) can be found in Makefile. Hence, -you need to adapt it there. You can then build and install the toolkit into -a prefixed path like: +belong into a package binary of a distribution. Hence, you might want to build +the toolkit with: + + $ make DISTRO=1 + +A hardening option is also available via HARDENING=1 if needed. You can then +build and install the toolkit into prefixed path like: $ make PREFIX= $ make PREFIX= install -Thanks for maintaining netsniff-ng in your distribution. Further questions -will be answered on the public mailing list. +Thanks for maintaining netsniff-ng in your distribution. Further questions will +be answered on the public mailing list. Last but not least, there is one small utility for advanced users that we have not integrated into the main build process. This is a minimal BPF JIT image -- cgit v1.2.3-54-g00ecf