Skip to content

Depend on upstream version of cortex-m #1

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

Closed
hannobraun opened this issue Nov 27, 2017 · 1 comment
Closed

Depend on upstream version of cortex-m #1

hannobraun opened this issue Nov 27, 2017 · 1 comment

Comments

@hannobraun
Copy link
Member

We're currently depending on my fork of cortex-m, as the upstream version won't build correctly for us. I've submitted a pull request.

@hannobraun
Copy link
Member Author

A fix for the issue has been merged upstream, but it's been released together with some breaking changes that I'm not yet ready for. Since we don't depend directly on my cortex-m fork, instead [patch]ing it in Cargo.toml, it should be fine to leave this as is for the time being.

This issue will be properly fixed later, when we upgrade to cortex-m 0.4.x. This is going to be part of a larger effort, as other changes need to make their way downstream from svd2rust via lpc82x at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant