build: require explicit bundled WeeChat header - #48
Merged
Conversation
This was referenced Jul 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stop silently falling back to the bundled
weechat-plugin.hwhen the system header cannot be found.The default path now fails with a message telling the builder to install WeeChat development headers, set
WEECHAT_PLUGIN_FILE, or explicitly opt into the bundled header withWEECHAT_BUNDLED=true. The bundled path still works when requested.Validation:
cargo fmt --checkgit diff --checkWEECHAT_BUNDLED=true CARGO_TARGET_DIR=/home/kom/tmp/rust-weechat-target-bundled cargo check -p weechat-sys --lockedWEECHAT_BUNDLED/WEECHAT_PLUGIN_FILE, with the new explicit error textReferences poljar/weechat-matrix-rs#124.