6b70dd6d39
This was the only way I knew how to display the step at which the build-setup process failed. I've personally experienced failures at multiple of the build steps, and before I got used to Chipyard, it was hard to figure out which step was the culprit. With this, users should have a bit more info to troubleshoot their issues. For some of the build steps that required multiple lines, I figured it made more sense to put them into a sub-script, rather than putting a && at the end of each line. But for the firesim one for example, since it was two .sh calls, I just put a && after the first one, inside of the try block, to make sure both lines run.
22 lines
741 B
Bash
Executable File
22 lines
741 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
# This script is intended to be used as a sub-step of build-setup.sh.
|
|
|
|
# note: lock file must end in .conda-lock.yml - see https://github.com/conda-incubator/conda-lock/issues/154
|
|
set -e
|
|
CONDA_REQS=$CYDIR/conda-reqs
|
|
CONDA_LOCK_REQS=$CONDA_REQS/conda-lock-reqs
|
|
# must match with the file generated by generate-conda-lockfile.sh
|
|
LOCKFILE=$CONDA_LOCK_REQS/conda-requirements-$TOOLCHAIN_TYPE-linux-64.conda-lock.yml
|
|
|
|
if [ "$USE_UNPINNED_DEPS" = true ]; then
|
|
# auto-gen the lockfiles
|
|
$CYDIR/scripts/generate-conda-lockfiles.sh
|
|
fi
|
|
|
|
# use conda-lock to create env
|
|
conda-lock install --conda $(which conda) -p $CYDIR/.conda-env $LOCKFILE
|
|
|
|
source $CYDIR/.conda-env/etc/profile.d/conda.sh
|
|
conda activate $CYDIR/.conda-env
|