e9c6594264
Most examples have in their makefiles a default RTE_TARGET directory to be
used in case RTE_TARGET is not set. Rather than just using a hard-coded
default, we can instead detect what the build directory is relative to
RTE_SDK directory.
This fixes a potential issue for anyone who continues to build using
"make install T=x86_64-native-linuxapp-gcc" and skips setting RTE_TARGET
explicitly, instead relying on the fact that they were building in a
directory which corresponded to the example default path - which was
changed to "x86_64-native-linux-gcc" by commit 218c4e68c1 ("mk: use
linux and freebsd in config names").
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
19 lines
608 B
Makefile
19 lines
608 B
Makefile
# SPDX-License-Identifier: BSD-3-Clause
|
|
# Copyright(c) 2010-2014 Intel Corporation
|
|
|
|
ifeq ($(RTE_SDK),)
|
|
$(error "Please define RTE_SDK environment variable")
|
|
endif
|
|
|
|
# Default target, detect a build directory, by looking for a path with a .config
|
|
RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config)))))
|
|
|
|
include $(RTE_SDK)/mk/rte.vars.mk
|
|
|
|
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += client_server_mp
|
|
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += simple_mp
|
|
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += symmetric_mp
|
|
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += hotplug_mp
|
|
|
|
include $(RTE_SDK)/mk/rte.extsubdir.mk
|