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

Add cargo-generate url and bin file for aarch64-unknown-linux-gnu #89

Merged
merged 1 commit into from
Jun 27, 2022

Conversation

SergioGasquez
Copy link
Member

@SergioGasquez SergioGasquez commented Jun 16, 2022

Since cargo-generate/cargo-generate/pull/620 got merged, from release 0.15.2 we can now use binary package for aarch64-unknown-linux-gnu

@SergioGasquez SergioGasquez marked this pull request as ready for review June 17, 2022 10:57
@georgik georgik changed the base branch from main to build/1.62.0.0 June 27, 2022 12:05
@georgik georgik added this to the v1.62 milestone Jun 27, 2022
@georgik georgik added the CI label Jun 27, 2022
@georgik georgik merged commit 103b647 into build/1.62.0.0 Jun 27, 2022
@SergioGasquez SergioGasquez deleted the feature/cargo-generate-update branch June 27, 2022 12:49
georgik added a commit that referenced this pull request Jul 13, 2022
* ci: update version to 1.62.0.0
* Installer improvements (#88)
* Use nightly toolchain with profile-minimal
* Install llvm clang only for Xtensa targets
* Add cargo-generate url and bin file for aarch64-unknown-linux-gnu (#89)
* Support `--build-target all` (#92)
* Fix ldproxy links (#94)
* ci: add system package dependency on openssl
* Remove PIP_USER (#96)
* Remove espmonitor (#99)
- replaced by functionality in espflash
* Add `ldproxy` binary for `aarch64-unknown-linux-gnu` (#100)
* Update espflash and cargo-espflash binaries (#103)
* Fix: Use cargo-espflash binary (#105)

Co-authored-by: Sergio Gasquez Arcos <sergio.gasquez@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants