aboutsummaryrefslogtreecommitdiffstats
path: root/fpga/usrp3/lib/sim/dsp
diff options
context:
space:
mode:
authorHumberto Jimenez <humberto.jimenez@ni.com>2020-04-13 14:48:48 -0500
committerWade Fife <wade.fife@ettus.com>2020-04-14 10:43:51 -0500
commit932b7cbb040cef7fce0c83f81839722fd8ad5bdf (patch)
tree316d7ea8b825632b37099868663de3813ad71491 /fpga/usrp3/lib/sim/dsp
parent9d6d26ca350b9cc055a556dd420d56f48384ddf4 (diff)
downloaduhd-932b7cbb040cef7fce0c83f81839722fd8ad5bdf.tar.gz
uhd-932b7cbb040cef7fce0c83f81839722fd8ad5bdf.tar.bz2
uhd-932b7cbb040cef7fce0c83f81839722fd8ad5bdf.zip
fpga: tools: Option to check for full Vivado version
This commits enables the FPGA build infrastructure to require a very specific Vivado version, all the way to the patch level. Vivado typically has the following version format: Year.release.update_patch This commit enables setupenv_base.sh to optionally look for the environment variable VIVADO_VER_FULL, which should contain the full Vivado version in the format specified above. Vivado is directly used to retrieve the installed version, returning an error if the requested version is not found. Example in setupenv.sh (which calls setupenv_base.sh): VIVADO_VER=2019.1 VIVADO_VER_FULL=2019.1.1_AR73068 The setupenv.sh script will setup Vivado 2019.1, but it will also verify that both Update 1 and patch AR73068 are installed.
Diffstat (limited to 'fpga/usrp3/lib/sim/dsp')
0 files changed, 0 insertions, 0 deletions