Skip to content

Rust wrapper: Remove unused aes_cts cfg detection - #11402

Open
holtrop-wolfssl wants to merge 1 commit into
wolfSSL:masterfrom
holtrop-wolfssl:f-8294
Open

Rust wrapper: Remove unused aes_cts cfg detection#11402
holtrop-wolfssl wants to merge 1 commit into
wolfSSL:masterfrom
holtrop-wolfssl:f-8294

Conversation

@holtrop-wolfssl

Copy link
Copy Markdown
Contributor

Description

Rust wrapper: Remove unused aes_cts cfg detection

Fixes F-8294.

Testing

How did you test?

Checklist

  • added tests
  • updated/added doxygen
  • updated appropriate READMEs
  • Updated manual and documentation

@holtrop-wolfssl holtrop-wolfssl self-assigned this Sep 8, 2026
Copilot AI lite review requested due to automatic review settings September 8, 2026 19:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

The removed cfg (aes_cts) is not used anywhere in the Rust wrapper sources, so this is a safe dead-code cleanup with no behavioral impact.

Pull request overview

This PR simplifies the Rust wolfcrypt wrapper build script by removing cfg auto-detection for AES-CTS, which is not referenced anywhere in the Rust wrapper code and therefore never affected compilation output.

Changes:

  • Removed wc_AesCtsEncrypt-based cfg probing (aes_cts) from scan_cfg() in the Rust wrapper build script.
File summaries
File Description
wrapper/rust/wolfssl-wolfcrypt/build.rs Drops unused AES-CTS cfg detection to reduce build-script surface area and unnecessary cfg emission.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@holtrop-wolfssl

Copy link
Copy Markdown
Contributor Author

retest this please ([Checks API] No suitable checks publisher found.
Finished: FAILURE)

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.

2 participants