Skip to content

Latest commit

 

History

History
102 lines (69 loc) · 3.32 KB

README.md

File metadata and controls

102 lines (69 loc) · 3.32 KB
Raw

About riscv-tools

Home: https://github.com/ucb-bar/riscv-tools-feedstock

Package license:

Feedstock license: BSD-3-Clause

Summary: RISC-V toolchain for UC Berkeley projects

Current build status

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing riscv-tools

Installing riscv-tools from the ucb-bar channel can be achieved by adding ucb-bar to your channels with:

conda config --add channels ucb-bar
conda config --set channel_priority strict

Once the ucb-bar channel has been enabled, riscv-tools can be installed with conda:

conda install riscv-tools

or with mamba:

mamba install riscv-tools

It is possible to list all of the versions of riscv-tools available on your platform with conda:

conda search riscv-tools --channel ucb-bar

or with mamba:

mamba search riscv-tools --channel ucb-bar

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search riscv-tools --channel ucb-bar

# List packages depending on `riscv-tools`:
mamba repoquery whoneeds riscv-tools --channel ucb-bar

# List dependencies of `riscv-tools`:
mamba repoquery depends riscv-tools --channel ucb-bar

Updating riscv-tools-feedstock

If you would like to improve the riscv-tools recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the ucb-bar channel, whereupon the built conda packages will be available for everybody to install and use from the ucb-bar channel. Note that all branches in the conda-forge/riscv-tools-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers