nandi/jolt-native · fixups.toml

⑂ 8cf1b3347ef6fa83297b6866dfd47d2728d4e339

fixups.toml · 11 lines · 699 BTOML    Blame HistoryRaw
Build both objects under buck2, against the BuildBuddy cache   1# aws-lc-rs's build script only re-exports what aws-lc-sys published through
2# cargo's `links` metadata, and buck2 does not carry that between build
3# scripts: it asserts on the first `DEP_AWS_LC_<version>_INCLUDE` it finds and
4# panics with "missing DEP_AWS_LC_ include" when there is none. The name
5# encodes aws-lc-sys's `links = "aws_lc_0_43_0"`, and the value is the header
6# directory in that crate's own sources.
8# Both halves name the version, and nothing here derives it: bumping aws-lc-sys
9# means editing this file, and the symptom of forgetting is that same panic.
10[buildscript.run]
11env = { DEP_AWS_LC_0_43_0_INCLUDE = "$(location :aws-lc-sys-0.43.0.crate)/include", OPT_LEVEL = "2" }

Build both objects under buck2, against the BuildBuddy cache 600f207 nandi 19d ago	1	# aws-lc-rs's build script only re-exports what aws-lc-sys published through
	2	# cargo's `links` metadata, and buck2 does not carry that between build
	3	# scripts: it asserts on the first `DEP_AWS_LC_<version>_INCLUDE` it finds and
	4	# panics with "missing DEP_AWS_LC_ include" when there is none. The name
	5	# encodes aws-lc-sys's `links = "aws_lc_0_43_0"`, and the value is the header
	6	# directory in that crate's own sources.
	7	#
	8	# Both halves name the version, and nothing here derives it: bumping aws-lc-sys
	9	# means editing this file, and the symptom of forgetting is that same panic.
	10	[buildscript.run]
	11	env = { DEP_AWS_LC_0_43_0_INCLUDE = "$(location :aws-lc-sys-0.43.0.crate)/include", OPT_LEVEL = "2" }