kismet: fix build when none of client, server or drone are selected

Random package configuration can trigger the selection of kismet, but
neither of client, server or drone suboptions. In this case, the
KISMET_TARGET_BINARIES variable is empty, leading to failure during
the installation stage.

At the same time, we remove the useless stripping of the installed
binaries, since this is done globally by the Buildroot infrastructure.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Thomas Petazzoni 2010-08-29 19:38:04 +02:00 committed by Peter Korsgaard
parent d6d6ff6a9c
commit 2ab8ec9e26
2 changed files with 8 additions and 6 deletions

View File

@ -18,9 +18,10 @@
fs: old-style squashfs for big endian archs fixed.
Updated/fixed packages: busybox, gst-plugins-base,
imagemagick, libgail, libglib2, libgtk2, lua, luafilesystem,
lzo, ncurses, netcat, pango, php, pppd, proftpd, qt, samba,
startup-notification, swfdec, sysvinit, util-linux
imagemagick, kismet, libgail, libglib2, libgtk2, lua,
luafilesystem, lzo, ncurses, netcat, pango, php, pppd,
proftpd, qt, samba, startup-notification, swfdec, sysvinit,
util-linux
Removed packages: stunnel

View File

@ -33,18 +33,19 @@ $(eval $(call AUTOTARGETS,package,kismet))
$(KISMET_TARGET_INSTALL_TARGET):
$(call MESSAGE,"Installing")
ifdef KISMET_TARGET_BINARIES
$(INSTALL) -m 755 $(addprefix $(KISMET_DIR)/, $(KISMET_TARGET_BINARIES)) $(TARGET_DIR)/usr/bin
endif
ifdef KISMET_TARGET_CONFIGS
$(INSTALL) -m 644 $(addprefix $(KISMET_DIR)/conf/, $(KISMET_TARGET_CONFIGS)) $(TARGET_DIR)/etc
endif
ifeq ($(BR2_ENABLE_DEBUG),)
$(STRIPCMD) $(STRIP_STRIP_ALL) $(addprefix $(TARGET_DIR)/usr/bin/, $(KISMET_TARGET_BINARIES))
endif
touch $@
$(KISMET_TARGET_UNINSTALL):
$(call MESSAGE,"Uninstalling")
ifdef KISMET_TARGET_BINARIES
rm -f $(addprefix $(TARGET_DIR)/usr/bin/, $(KISMET_TARGET_BINARIES))
endif
ifdef KISMET_TARGET_CONFIGS
rm -f $(addprefix $(TARGET_DIR)/etc/, $(KISMET_TARGET_CONFIGS))
endif