2022-12-01 03:02:36 -06:00
|
|
|
# only-macos
|
|
|
|
|
#
|
|
|
|
|
# Check that a set deployment target actually makes it to the linker.
|
|
|
|
|
# This is important since its a compatibility hazard. The linker will
|
|
|
|
|
# generate load commands differently based on what minimum OS it can assume.
|
|
|
|
|
|
2023-03-30 07:58:50 -05:00
|
|
|
include ../tools.mk
|
2022-12-01 03:02:36 -06:00
|
|
|
|
|
|
|
|
ifeq ($(strip $(shell uname -m)),arm64)
|
|
|
|
|
GREP_PATTERN = "minos 11.0"
|
|
|
|
|
else
|
2022-11-13 16:58:18 -06:00
|
|
|
GREP_PATTERN = "version 10.13"
|
2022-12-01 03:02:36 -06:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
OUT_FILE=$(TMPDIR)/with_deployment_target.dylib
|
|
|
|
|
all:
|
2022-11-13 16:58:18 -06:00
|
|
|
env MACOSX_DEPLOYMENT_TARGET=10.13 $(RUSTC) with_deployment_target.rs -o $(OUT_FILE)
|
2022-12-01 03:02:36 -06:00
|
|
|
# XXX: The check is for either the x86_64 minimum OR the aarch64 minimum (M1 starts at macOS 11).
|
|
|
|
|
# They also use different load commands, so we let that change with each too. The aarch64 check
|
|
|
|
|
# isn't as robust as the x86 one, but testing both seems unneeded.
|
|
|
|
|
vtool -show-build $(OUT_FILE) | $(CGREP) -e $(GREP_PATTERN)
|
