Package Details: vivado 2024.2-1

Git Clone URL: https://aur.archlinux.org/vivado.git (read-only, click to copy)
Package Base: vivado
Description: FPGA/CPLD design suite for AMD devices – Vivado edition
Upstream URL: https://www.xilinx.com/products/design-tools/vivado.html
Licenses: custom
Conflicts: vitis
Submitter: xiretza
Maintainer: VitalyR (leuko)
Last Packager: leuko
Votes: 17
Popularity: 0.031913
First Submitted: 2019-06-18 22:23 (UTC)
Last Updated: 2024-11-20 22:25 (UTC)

Pinned Comments

leuko commented on 2024-01-14 21:14 (UTC) (edited on 2024-09-26 06:41 (UTC) by leuko)

PKGBUILD cannot download Vivado, you have to download Vivado before executing the PKGBUILD. Refer to PKGBUILD.

This PKGBUILD is also able to install Vitis with some errors, however there is a standalone package called vitis AUR which seems to be more advanced than the installation in this PKGBUILD.

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »

Focshole commented on 2020-03-04 15:11 (UTC) (edited on 2020-03-04 15:13 (UTC) by Focshole)

@xiretza: Fixed, it was a problem with an unofficial repo (Blackarch). Installing ncurses5-compat-libs from AUR fixed it. I'm clearing and reviewing all the other posts to avoid useless cluttering.

xiretza commented on 2020-03-04 14:34 (UTC)

@Focshole: the correct way is to install the old curses libraries, i.e. ncurses5-compat-libs. That's what the dependency is for.

xiretza commented on 2020-03-04 12:20 (UTC)

@Focshole: I might add manual extraction soon since a new pacman release doesn't seem to be anywhere close.

/usr/lib/libtinfo.so.5 is provided by ncurses5-compat-libs, which is a dependency of this package - did you actually have a problem or did you just create the symlink as a misguided precaution (that's usually a horrible idea by the way, so-versions exist for a reason).

Focshole commented on 2020-03-04 10:43 (UTC) (edited on 2020-03-04 15:09 (UTC) by Focshole)

To update to last version (at least, it worked for me):

0) setting my aur helper working directory somewhere else (/tmp couldn't fit it)

1)updated pkgver, _more_ver and md5sum

2)in package() I added at the beginning:

tar -xrf Xilinx_Vivado_${pkgver}_${_more_ver}"

cd "Xilinx_Vivado_${pkgver}_${_more_ver}" (removed "SDK" word)

3)replace 2019.1 with 2019.2 in the "install udev rules"

If libtinfo.so.5 is missing (https://forums.xilinx.com/t5/Installation-and-Licensing/Installing-Vivado-2018-1-on-Fedora-28/td-p/855996), then check if it was installed from aur (Blackarch repo has a broken version)

CptnHddck commented on 2020-01-12 15:32 (UTC)

Thanks for this package [got my vote]. Used it to install Vivado 2019.2 on Manjaro 18.1.4 (using Pamac) after the Xilinx unified installer did not work (allegedly supports only a few distros). Verified functionality with Arty A7 FPGA dev board. Had to tweak the package file (obviously due to the different version => different hash). Also, libfakeroot was not found and I specified the absolute path to work around it. Added manual decompression of the tar.gz archive. As pointed out by the package file, the archive is rather big (26.5 GiB) and installation failed at the beginning because of the available disk space (had 150GiB in total); enlarged partition to work around this.

xiretza commented on 2019-11-29 09:06 (UTC)

Package currently doesn't build due to a makepkg bug. As soon as https://git.archlinux.org/pacman.git/commit/?id=349c22d043290ccd0cce9f30981f5415e295442a lands in a release, I can update it to 2019.2.

xw258 commented on 2019-10-31 13:43 (UTC)

@xiretza: that may explain. i built it directly under host env containing xorg, so my builds had libawt_xawt.so while your build did not. but that's just my guess.

and it took me too much time to build vivado... so i do not want to build it again until the next version. i will give a feedback at the next version if you made some patches, or a workaround patch if you did not.

xiretza commented on 2019-10-15 11:54 (UTC)

@heliochronix: cheers, the package now includes desktop files and udev rules!

heliochronix commented on 2019-10-14 19:00 (UTC)

@xiretza: I sent you a patch file via email. Hope it helps!

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »