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

Missing libuavcan_dsdlc in v1.0 #278

Closed
jxltom opened this issue Feb 19, 2020 · 3 comments
Closed

Missing libuavcan_dsdlc in v1.0 #278

jxltom opened this issue Feb 19, 2020 · 3 comments

Comments

@jxltom
Copy link

jxltom commented Feb 19, 2020

I would like to try libuavcan v1.0 as suggested in https://uavcan.org/, but I found the libuavcan_dsdlc tool is missing in https://github.com/UAVCAN/libuavcan/tree/uavcan-v1.0. Besides, it looks like there is no docs and examples in v1.0. The can drivers are also missing.

What is the status of libuavcan v1.0? Are there any tutorials for v1? If not, should I still use v0 instead? Many thanks!

@thirtytwobits
Copy link
Contributor

I'm very sorry but libuavcan v1.0 isn't ready yet :( It's not abandoned though, it's just that the standardization process for the core specification is taking all my development time up right now. We are looking for additional contributors to speed things up if you are interested but I will be back to this within a month or two.

You can look at libcanard for the C implementation that is progressing more quickly and pyuavcan v1 is ready to go.

Also, libuavcan v1.0 will no longer using libuavcan_dsdlc. Instead we will use nunavut to generate C++ from DSDL in this version. Nunavut will become the unified code generator for the project when it is complete. You can watch my progress on C++ type serialization on my fork here. Sorry again. Please contribute, if not check back in a few months for more progress.

V0 is mature so using it is always an option. The V1 specification is in "alpha" and we are working with industry leaders to make it a formal specification with long term support.

@jxltom
Copy link
Author

jxltom commented Feb 20, 2020

Thanks for the explanation. I will keep using v0 for now and look forward to the release of v1!

@pavel-kirienko
Copy link
Member

Closing as duplicate of #277.

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

No branches or pull requests

3 participants