
This is something I hadn't previously done, but there are cases where it's needed, e.g., building 'wlantest' and then one of the tests/fuzzing/*/ projects, they use a different configuration (fuzzing vs. not fuzzing). Perhaps more importantly, this gets rid of the last thing that was dumped into the source directories, apart from the binaries themselves. Note that due to the use of thin archives, this required building with absolute paths. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
40 lines
601 B
Makefile
40 lines
601 B
Makefile
ALL=$(OUT)libutils.a
|
|
|
|
include ../lib.rules
|
|
|
|
install:
|
|
@echo Nothing to be made.
|
|
|
|
|
|
#CFLAGS += -DWPA_TRACE
|
|
CFLAGS += -DCONFIG_IPV6
|
|
CFLAGS += -DCONFIG_DEBUG_FILE
|
|
|
|
LIB_OBJS= \
|
|
base64.o \
|
|
bitfield.o \
|
|
common.o \
|
|
crc32.o \
|
|
ip_addr.o \
|
|
json.o \
|
|
radiotap.o \
|
|
trace.o \
|
|
uuid.o \
|
|
wpa_debug.o \
|
|
wpabuf.o
|
|
|
|
# Pick correct OS wrapper implementation
|
|
LIB_OBJS += os_unix.o
|
|
|
|
# Pick correct event loop implementation
|
|
LIB_OBJS += eloop.o
|
|
|
|
# Pick correct edit implementation
|
|
LIB_OBJS += edit.o
|
|
|
|
#LIB_OBJS += pcsc_funcs.o
|
|
|
|
_OBJS_VAR := LIB_OBJS
|
|
include ../objs.mk
|
|
$(OUT)libutils.a: $(LIB_OBJS)
|
|
$(AR) crT $@ $?
|