Skip to content

Conversation

ZuseZ4
Copy link
Member

@ZuseZ4 ZuseZ4 commented Oct 23, 2025

For testing I just added the whole cmake folder for now, we might want to reduce it just to the LLVMconfig.cmake file later.
Based on some local comparisons between a x.py dist rust-dev folder structure and the ci-llvm folder structure (and where enzyme is looking) I think this should end up at the right location.

What would be the best way without merging to test that locally or in CI to verify that Enzyme now works?

  1. Do a local x.py dist rust-dev build

  2. Build rust+enzyme with download-ci-llvm, wait till it fails.

  3. Delete the ci-llvm folder and replace it with the component from 1., which now includes the cmake files?

    r? @Kobzol

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Oct 23, 2025
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants