-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add an example that works with coap and riot in rust #131
base: main
Are you sure you want to change the base?
Conversation
This may look neater when the coapserver-coaphandler example is split into a library and a runtime part -- then we could share code. Also, I plan on having a client example on the same kind of API, which would allow us to run RIOT device-to-device demos. |
Hitting some issues apparently coming from First, I updated the channel to Then, got the following: Details
Note that previously I had issues with Version of |
Updating proc-macro2 is an unfortunate necessity when using nightly -- for reasons I haven't looked up yet, that crate insists on using nightly features when running on nightly, consequently breaking every other time you're running with an old nightly and new crate or vice versa. A cargo update usually does the trick. RIOT should build fine now on stable, though, so maybe this can all be built on stable anyway (and thus race less trouble with bindgen). BTW, the client version of this is a bit backlogged because I'm running into a weird lifetime issue for setting payload, I may need to add a less powerful API there initially. |
Thanks for the update. I still get the same result after |
Hm, I've removed the obstacles for using stable (pushed to an own branch as I'm not a project member and can thus not push onto yours), and the problem persists; digging. |
Thanks for the update. Added you as collaborator in my fork. |
OK, sent a bunch of updates.
Now this would be testable if only |
We'll yet have to find a way to deal with |
A nasty fix would be to remove - run: cargo fmt --check
+ run: |
+ sed -i -E "s/rust_riotmodules.*//g" examples/coap-riot/Cargo.toml # avoiding cargo `fmt issues` in coap rust example
+ cargo fmt --check |
Now that RIOT-OS/rust-riot-wrappers#67 is merged, the special branch is not there any more, but the default branch should do nicely. Ad fmt: It's nasty indeed, but for the moment I guess it'll work. Will you do the next round of changes? (I think this is otherwise quite ready -- at least with the software implementation, PSA would be next). |
…ver-coaphandler.rs The random interface introduced in riot-wrappers is used to fill the gap introduced since then.
This reflects an equivalent line in the coap-message-demos example for std
… implementing the right traits
1951205
to
781f351
Compare
No description provided.