-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathMakefile
More file actions
35 lines (29 loc) · 1.47 KB
/
Makefile
File metadata and controls
35 lines (29 loc) · 1.47 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
PROJ_DIR := $(dir $(abspath $(lastword $(MAKEFILE_LIST))))
EXT_NAME = dplyr
EXT_CONFIG = ${PROJ_DIR}extension_config.cmake
# Keep Rust artifacts in a deterministic place for repeated builds.
export CARGO_TARGET_DIR ?= ${PROJ_DIR}target
export DUCKDB_EXTENSION_PATH ?= ${PROJ_DIR}build/release/extension/dplyr
include extension-ci-tools/makefiles/duckdb_extension.Makefile
# WASM builds require the Rust wasm32-unknown-emscripten target.
# extension-ci-tools' WASM targets depend on `wasm_pre_build_step`, so we
# override it here (without patching the submodule) to ensure the target exists.
wasm_pre_build_step:
@if command -v rustup >/dev/null 2>&1; then \
toolchain="$${RUSTUP_TOOLCHAIN:-stable}"; \
echo "Ensuring Rust target wasm32-unknown-emscripten is installed for toolchain $${toolchain}"; \
rustup target add --toolchain "$${toolchain}" wasm32-unknown-emscripten; \
else \
echo "rustup not found; cannot install wasm32-unknown-emscripten target"; \
exit 1; \
fi
# Submodule policy: keep `duckdb` and `extension-ci-tools` pinned to exact commits.
# Do not use `git submodule update --remote` except in an explicit PR updating the pin.
.PHONY: submodules submodules-init
submodules:
@echo "Updating submodules to pinned commits (no --remote). See docs/submodules.md."
@git submodule update --init --recursive
submodules-init:
@echo "Initializing submodules to pinned commits (no --remote). See docs/submodules.md."
@git submodule init
@git submodule update --init --recursive