javy/Makefile at main · bytecodealliance/javy · GitHub

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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
.PHONY: fmt fmt-check lint-wasi-targets lint-wasip1-targets lint-wasip2-targets \
	test-wasi-targets test-wasip1-targets test-wasip2-targets wasi-targets \
	lint-native-targets lint-native-targets-ci test-native-targets \
	test-native-targets-ci native-targets test-wpt test-wpt-ci test-all \
	clean cli build-default-plugin build-test-plugins ci
.DEFAULT_GOAL := cli

# Selection for linting / testing.
#
# Definitions are expected in`[package.metadata.javy]` in the
# corresponding Cargo.toml:
#
#   targets = ["native" | "wasip1" | "wasip2"]
#
# Note that if no targets are defined, the default is [ "native" ]
#
# Whether a crate has tests is read from cargo's own per-target `test`
# flag (e.g. `[lib] test = false`), so test-only fixtures opt out via
# the standard cargo manifest rather than custom metadata.  The
# auxiliary plugin crates (javy-test-plugin-wasi{p1, p2}) are
# currently the only crates exempt from unit/integration testing.
#
# Expected arguments:
#   1: target tag,
#   2: "lint" or "test"
define select_crates_for
$(shell cargo metadata --format-version=1 --no-deps | jq -r \
  --arg tgt $(1) --arg mode $(2) '\
    .packages[] \
    | (.metadata.javy.targets // ["native"]) as $$tgts \
    | (.targets | any(.test)) as $$has_tests \
    | select($$tgts | any(. == $$tgt)) \
    | select($$mode == "lint" or $$has_tests) \
    | "-p \(.name)"')
endef

NATIVE_LINT_CRATES := $(call select_crates_for,native,lint)
NATIVE_TEST_CRATES := $(call select_crates_for,native,test)
WASIP1_LINT_CRATES := $(call select_crates_for,wasip1,lint)
WASIP1_TEST_CRATES := $(call select_crates_for,wasip1,test)
WASIP2_LINT_CRATES := $(call select_crates_for,wasip2,lint)
WASIP2_TEST_CRATES := $(call select_crates_for,wasip2,test)

# === Format checks ===
fmt-check:
	cargo fmt --all --check
fmt:
	cargo fmt --all

# === Lint & Test WASI Targets ===
lint-wasi-targets: fmt-check lint-wasip1-targets lint-wasip2-targets

lint-wasip1-targets:
	cargo clippy $(WASIP1_LINT_CRATES) \
	--target=wasm32-wasip1 --all-targets --all-features -- -D warnings

lint-wasip2-targets:
	cargo clippy $(WASIP2_LINT_CRATES) \
	--target=wasm32-wasip2 --all-targets --all-features -- -D warnings

test-wasi-targets: test-wasip1-targets test-wasip2-targets

test-wasip1-targets:
	cargo hack test $(WASIP1_TEST_CRATES) \
	--target=wasm32-wasip1 --each-feature -- --nocapture

test-wasip2-targets:
	cargo hack test $(WASIP2_TEST_CRATES) \
	--target=wasm32-wasip2 --each-feature -- --nocapture

wasi-targets: lint-wasi-targets test-wasi-targets

# === Lint & Test Native Targets ===
lint-native-targets: build-default-plugin lint-native-targets-ci

lint-native-targets-ci: fmt-check
	CARGO_PROFILE_RELEASE_LTO=off cargo clippy $(NATIVE_LINT_CRATES) \
	--release --all-targets --all-features -- -D warnings

test-native-targets: build-default-plugin build-test-plugins test-native-targets-ci

# This command assumes a CI environment in which the test plugin
# assets have been previously created in the expected directories.
# This ensures that we can recycle CI time.
test-native-targets-ci:
	CARGO_PROFILE_RELEASE_LTO=off cargo hack test $(NATIVE_TEST_CRATES) \
	--release --each-feature -- --nocapture


native-targets: lint-native-targets test-native-targets

# === Web Platform Tests

# For usage in CI, in which we assume pre-existing assets.
test-wpt-ci:
	pnpm -C wpt install
	pnpm -C wpt test

test-wpt: cli test-wpt-ci

# === All tests ===
test-all: wasi-targets native-targets test-wpt


# === Misc ===
clean:
	cargo clean

# Intended to simulate what the GitHub Actions CI workflow will run.
# We don't invoke this directly because we often run out of disk space in
# GitHub Actions if we try to compile native targets in the same workflow as
# WASI targets so we have to use a multi-step process in GitHub to avoid that.
ci: lint-wasi-targets lint-native-targets test-all

# First, build the default plugin, which is a dependency to the CLI.
# No need to run `javy_plugin_processing`, the CLI build.rs will take
# care of doing that.
cli: build-default-plugin
	CARGO_PROFILE_RELEASE_LTO=off cargo build -p=javy-cli --release

# Build the default plugin
build-default-plugin:
	cargo build -p=javy-plugin --target=wasm32-wasip1 --release

# Build auxiliary plugins, for testing
build-test-plugins:
	cargo build --package=javy-test-plugin-wasip1 --target=wasm32-wasip1 --release
	cargo build --package=javy-test-plugin-wasip2 --target=wasm32-wasip2 --release
	cargo build --package=javy-test-invalid-plugin --target=wasm32-unknown-unknown --release
	cargo run --package=javy-plugin-processing --release -- target/wasm32-wasip1/release/test_plugin.wasm target/wasm32-wasip1/release/test_plugin.wasm
	cargo run --package=javy-plugin-processing --release -- target/wasm32-wasip2/release/test_plugin.wasm target/wasm32-wasip2/release/test_plugin.wasm