Skip to content

Use toolchains instead of aliases for platform selection#1801

Merged
phst merged 1 commit intomasterfrom
toolchain
Mar 30, 2026
Merged

Use toolchains instead of aliases for platform selection#1801
phst merged 1 commit intomasterfrom
toolchain

Conversation

@phst
Copy link
Copy Markdown
Owner

@phst phst commented Mar 30, 2026

Following https://bazel.build/extending/toolchains#toolchain-definitions, we should use separate toolchains for each supported combination of operating system and processor architecture.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces specific Emacs 29 and 30 toolchains for Windows x86_64, migrates toolchain dependencies to external repositories, and updates copyright years. The review identifies a critical issue where unsupported compatibility attributes were added to elisp_toolchain definitions, which will cause build errors and must be removed.

@phst phst force-pushed the toolchain branch 2 times, most recently from b600385 to 9ae4174 Compare March 30, 2026 15:47
Following https://bazel.build/extending/toolchains#toolchain-definitions, we
should use separate toolchains for each supported combination of operating
system and processor architecture.
@phst phst merged commit e22bbd4 into master Mar 30, 2026
18 checks passed
@phst phst deleted the toolchain branch March 30, 2026 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant