Closed newAM closed 3 years ago
This is how I'm solving it in heapless
to support both 0.2 and 0.3: https://github.com/japaric/heapless/pull/251
Might be of interest.
This is how I'm solving it in
heapless
to support both 0.2 and 0.3: japaric/heapless#251 Might be of interest.
That's a good idea, I updated it to use a range.
Looks ok to me, but there is a failure in build.
I cannot reproduce the same failure on Linux, and unfortunately I don't have a Windows install easily accessible right now.
Are you able to help me out with this?
please ping me once CI is fixed
Somebody on matrix pointed out the Windows build is not building for an embedded target, which is not supported by defmt: https://github.com/knurling-rs/defmt/issues/463
I fixed the failure by removing that build for Windows :sweat_smile:.
@jonas-schievink CI is fixed.
hmm, why did it work with 0.2?
hmm, why did it work with 0.2?
I did a quick scan through the code.
defmt
0.3 introduced some new global symbols for flushing:
These symbols get defined by the global logger:
I am guessing there is something about Windows that doesn't like GNU linker script or the export_name
attributes that were introduced for these new symbols.
bors r+
Thanks for the review & merge!
Would it be possible to get a 0.6.1
release with this change?
Published 0.6.1
Regarding the linker error, I don't think that's a problem with defmt 0.3.0 specifically, since https://github.com/stm32-rs/bxcan/pull/49 also fails to link again defmt 0.2.3 (https://github.com/stm32-rs/bxcan/runs/4213689874?check_suite_focus=true)
Update defmt (and other knurling-rs tools) to 0.3, see https://ferrous-systems.com/blog/defmt-3/