Skip to content

Conversation

SergioGasquez
Copy link
Member

  • Replace the current C stubs for esp-flasher-stub generated stubs.
    • esp-flasher-stub does not generate ESP8266 stubs so I kept the C based stub for it

@MabezDev
Copy link
Member

Given how untested the stubs are, this has the potential to induce a bunch of bug reports. Do we want to add them behind a flag first?

@SergioGasquez
Copy link
Member Author

Given how untested the stubs are, this has the potential to induce a bunch of bug reports. Do we want to add them behind a flag first?

I initially did that, but as Jesse suggested, not sure how many people will test it if it's behind a feature. Happy to revert the lats commit and keep it behind a flag, though.

@MabezDev
Copy link
Member

I initially did that, but as Jesse suggested, not sure how many people will test it if it's behind a feature

True, presumably there will be a rc release for espflash 3.0, so I guess if many people run into issues with the rc we can revisit the decision.

Copy link
Member

@jessebraham jessebraham left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@jessebraham jessebraham merged commit 775e222 into esp-rs:main Nov 23, 2023
@SergioGasquez SergioGasquez deleted the feat/rust-stub branch November 23, 2023 11:27
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.

Use esp-flasher-stub instead of the C-based stubs

3 participants