Skip to content

Conversation

NobodyXu
Copy link
Collaborator

@NobodyXu NobodyXu commented Aug 24, 2025

By extracting mod windows_registry out as a separate crate, we will have

  • more freedom of changing APIs to adopt to different needs of API without breaking cc API
  • users who only need windows-registry doesn't have to pull in entire cc
  • faster compilation since windows-registry codegen can be done in parallel to cc compilation, and windows-registry spends ~80% of time in codegen
image

@NobodyXu
Copy link
Collaborator Author

CI semver failed due to false positive obi1kenobi/cargo-semver-checks#638 , temporarily disabling it until another release is made

@NobodyXu NobodyXu marked this pull request as ready for review August 24, 2025 15:05
Copy link
Collaborator

@madsmtm madsmtm left a comment

Choose a reason for hiding this comment

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

Looks good with comments resolved.

@madsmtm madsmtm added the O-windows Windows targets and toolchains label Aug 25, 2025
@NobodyXu
Copy link
Collaborator Author

I have to rename the crate to windows-find-tools since windows-registry is already taken

https://crates.io/crates/windows-registry

@NobodyXu NobodyXu requested a review from madsmtm August 25, 2025 14:15
@NobodyXu NobodyXu changed the title Refactor: Extract windows registry Refactor: Extract windows-find-tools Aug 25, 2025
@NobodyXu NobodyXu requested a review from madsmtm August 26, 2025 14:12
Copy link
Collaborator

@madsmtm madsmtm left a comment

Choose a reason for hiding this comment

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

Thanks, looks good now (after nit)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-windows Windows targets and toolchains
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants