04-07-2020 12:25 PM
Hi,
I've written a Makefile to generate Vivado projects which was mostly developed on Linux.
We chose to use Make because on windows, it comes with the Vivado installer.
Our windows our procedure is:
My problem is that the shell scripts called when running /c/Xilinx/Vivado/2018.2/bin/vivado seem to not be compatible with the version of uname shipped with the Vivado installer:
$ which uname /usr/bin/uname $ uname MINGW64_NT-10.0 $ source /c/Xilinx/Vivado/2018.2/settings64.sh $ which uname C:\Xilinx\SDK\2018.2\gnuwin\bin\uname.EXE $ uname windows32
/c/Xilinx/Vivado/2018.2/bin/loader doesn't check for `uname` == `windows*`.
I'm wondering if my procedure is wrong or if this is a known issue.
Thanks,
Liam
06-01-2020 12:53 PM
Hi,
I fixed this but skipping setting64.sh completely.
$ cat ./win-setup.sh #!/bin/sh VERSION=2018.2 export PATH="${PATH}:/c/Xilinx/Vivado/${VERSION}/bin" export PATH="${PATH}:/c/Xilinx/SDK/${VERSION}/gnuwin/bin" $ source ./win-setup.sh $ vivado -help vivado Description: Vivado v2018.2 (64-bit) [ ... ]
06-01-2020 12:53 PM
Hi,
I fixed this but skipping setting64.sh completely.
$ cat ./win-setup.sh #!/bin/sh VERSION=2018.2 export PATH="${PATH}:/c/Xilinx/Vivado/${VERSION}/bin" export PATH="${PATH}:/c/Xilinx/SDK/${VERSION}/gnuwin/bin" $ source ./win-setup.sh $ vivado -help vivado Description: Vivado v2018.2 (64-bit) [ ... ]