Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make defmt::flush an no-operation when unstable-test feature is enabled #666

Merged
merged 1 commit into from
Mar 10, 2022

Conversation

japaric
Copy link
Member

@japaric japaric commented Mar 10, 2022

that feature is only enabled when running the test suite

defmt::flush was causing linker errors ("undefined symbol _defmt_acquire") on Windows with Rust
1.59.0+ when defmt is built with 'unstable-test' enabled. the linker errors are not observed in
binary builds that link to defmt when the feature is disabled

this commit removes the symbol dependencies to _defmt_acquire, etc. when 'unstable-test' is enabled

that feature is only enabled when running the test suite

defmt::flush was causing linker errors ("undefined symbol _defmt_acquire") on Windows with Rust
1.59.0+ when defmt is built with 'unstable-test' enabled. the linker errors are not observed in
binary builds that link to defmt

this commit removes the symbol dependencies to _defmt_acquire, etc. when 'unstable-test' is enabled
@japaric
Copy link
Member Author

japaric commented Mar 10, 2022

bors r=jonathanpallant

@bors
Copy link
Contributor

bors bot commented Mar 10, 2022

Build succeeded:

@bors bors bot merged commit 6a6c15e into main Mar 10, 2022
@bors bors bot deleted the fix-ci branch March 10, 2022 11:31
@Urhengulas
Copy link
Member

I honestly still don't understand why this was a problem for flush, but not for acquire, release. Can someone explain?

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.

3 participants