Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

espup installs potential riscv targets that are never used

Open
#388 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

Start by reproducing an espup installation and inspect the crosstool build artifacts for the four listed RISC-V targets. Confirm which targets Espressif tools actually use, then define whether espup should remove unused libraries or crosstool should stop producing them; done means unused targets are no longer installed without breaking the supported toolchain.

Written by the indexing model from the issue text.

Description

enhancement feature request

Bug description

If i understand it correctly espup just reuse the build-artifacts from crosstool. Currently it installs gcc libs for the following 4 targets in the case of the riscv eco-system.

  • rv32i_zicsr_zifencei
  • rv32imac_zicsr_zifencei
  • v32imafc_zicsr_zifencei
  • rv32imc_zicsr_zifencei
    This libs are relative huge, and if never used should not be installed.

To Reproduce

Steps to reproduce the behavior:

install esp toolchain with espup

Expected behavior

Only install tools that eventually will be used

Screenshots

Bildschirmfoto vom 2023-11-05 10-54-26

Proposal

If its true that we only use the imc and imac targets i would want that the installer directly delete the other for me ( simple option) or that croostool only produces that one that espressif uses.

Dominant language
Rust
Stars
460
Forks
37
Avg merge
2d 16h
Merged PRs (30d)
6

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from esp-rs/espup

All issues in esp-rs/espup

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.