summaryrefslogtreecommitdiff
path: root/kconfig
diff options
context:
space:
mode:
authorAlexey Neyman <stilor@att.net>2017-04-23 06:51:05 (GMT)
committerAlexey Neyman <stilor@att.net>2017-04-23 07:24:41 (GMT)
commit2f286ce5ab5f9938e504549726bf25acc5bdfe4b (patch)
tree62c4d52f6fcaddbf35bd66e84d618fdbaa335e3f /kconfig
parentf4c94242d450eb84b3f6fb533e86a6eaacee3152 (diff)
Retire BACKEND stuff
... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
Diffstat (limited to 'kconfig')
-rw-r--r--kconfig/kconfig.mk5
1 files changed, 0 insertions, 5 deletions
diff --git a/kconfig/kconfig.mk b/kconfig/kconfig.mk
index 955ae0b..c82e502 100644
--- a/kconfig/kconfig.mk
+++ b/kconfig/kconfig.mk
@@ -8,11 +8,6 @@
# Top file of crosstool-NG configuration
export KCONFIG_TOP = $(CT_LIB_DIR)/config/config.in
-export CT_IS_A_BACKEND:=$(CT_IS_A_BACKEND)
-export CT_BACKEND_ARCH:=$(CT_BACKEND_ARCH)
-export CT_BACKEND_KERNEL:=$(CT_BACKEND_KERNEL)
-export CT_BACKEND_LIBC:=$(CT_BACKEND_LIBC)
-
# We need CONF for savedefconfig in scripts/saveSample.sh
export CONF := $(CT_LIB_DIR)/kconfig/conf
MCONF := $(CT_LIB_DIR)/kconfig/mconf