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.
11 lines
246 B
Bash
11 lines
246 B
Bash
#!/usr/bin/env bash
|
|
|
|
# This script is intended to be used as a sub-step of build-setup.sh.
|
|
|
|
set -e
|
|
pushd $CYDIR/sims/verilator
|
|
make launch-sbt SBT_COMMAND=";project chipyard; compile"
|
|
make launch-sbt SBT_COMMAND=";project tapeout; compile"
|
|
popd
|
|
|