Skip to content

Don't distinguish between Regz generated code for "standalone"#773

Merged
mattnite merged 2 commits intomainfrom
regz-standalone-fix
Dec 22, 2025
Merged

Don't distinguish between Regz generated code for "standalone"#773
mattnite merged 2 commits intomainfrom
regz-standalone-fix

Conversation

@mattnite
Copy link
Contributor

Fixes #740.

We had a flag to make Regz generate code "for MicroZig". The point was to be able to output code that isn't tightly coupled to MicroZig, however the coupling is quite weak.

Instead I've removed that edge case so the imports for generated code always looks the same. To help those trying to use Regz output for a standalone project, I wrote a quick guide on what to implement for the microzig import.

Fixes #740.

We had a flag to make Regz generate code "for MicroZig". The point was
to be able to output code that isn't tightly coupled to MicroZig,
however the coupling is quite weak.

Instead I've removed that edge case so the imports for generated code
always looks the same. To help those trying to use Regz output for a
standalone project, I wrote a quick guide on what to implement for the
`microzig` import.
@mattnite mattnite force-pushed the regz-standalone-fix branch from 832203a to 9d18916 Compare December 22, 2025 22:27
@mattnite mattnite merged commit 60653a0 into main Dec 22, 2025
35 of 48 checks passed
@mattnite mattnite deleted the regz-standalone-fix branch December 22, 2025 22:46
@Grazfather
Copy link
Collaborator

Nice!

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.

regz: depends on microzig when generating standalone

2 participants