Closed thopiekar closed 4 years ago
Something I see in common with all errors is that they come from 32bit variables. Doesn't matter whether signed or unsigned. All the smaller datatypes like bytes or *Int16 are working.
I just can't see the reason still but investigating..
Details about Problem
nanoFramework area: Visual Studio extension (MDP)
VS version: 16.5.4
VS extension version: 2019.1.8.11
Target: STM32 F411RE (issue should be platform-independent)
Firmware image version: [master] (v1.0.3 is the latest release today)
Device capabilities output: None
Description
The generated code by MDP leads to datatype errors. The problem can likely be solved manually, but the idea of the original workflow should keep users away from the marshalling code and should only require to inject code into the marked sections.
Detailed repro steps so we can see the same problem
Generate native stub code with VS
Add interop to cmake-variants.json
Start rebuild
Get the errors below
...
Other suggested things
Nothing special, but the .cs-code below:
Expected behaviour
The generated code doesn't fail to compile. Normally, it should cause no conflicts since it doesn't have any custom code after generation and should compile itself while it does nothing.
Screenshot / Logs
Logs say more than words..
Additional context
Nope, not really.