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 .. 9 10 11 12 13 14

xiretza commented on 2019-10-13 00:42 (UTC)

@xw258: can't reproduce, it builds just fine in a clean base-devel chroot without libxtst.

xiretza commented on 2019-10-12 22:12 (UTC)

@heliochronix: could you send me a patch file? AUR comments break formatting a little.

heliochronix commented on 2019-10-11 20:58 (UTC) (edited on 2019-10-11 20:59 (UTC) by heliochronix)

Hello again,

I did some testing and actually found their script is terrible and that whole suggestion I had doesn't work. The changes I ended up making were as follows:

I added three new files based on the wiki:

Xilinx-DocNav.desktop

Xilinx-SDK.desktop

Xilinx-VivadoIDE.desktop

I added the relevant md5sums to the PKGBUILD.

I added the following install lines right before the Clean Up section that:

install -Dm644 "$pkgdir/opt/Xilinx/Vivado/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers/52-xilinx-digilent>

install -Dm644 "$pkgdir/opt/Xilinx/Vivado/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers/52-xilinx-ftdi-usb>

install -Dm644 "$pkgdir/opt/Xilinx/Vivado/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers/52-xilinx-pcusb.ru>

install -Dm644 "$srcdir/Xilinx-DocNav.desktop" -t "$pkgdir/usr/share/applications"

install -Dm644 "$srcdir/Xilinx-SDK.desktop" -t "$pkgdir/usr/share/applications"

install -Dm644 "$srcdir/Xilinx-VivadoIDE.desktop" -t "$pkgdir/usr/share/applications"

This seems to have resulted in effectively the same behavior as the driver install script, and also adds the desktop files so they can be located by the system. It all seems to build and install correctly, and I can interface with at least one of the FPGA boards I have access to via the udev rules.

heliochronix commented on 2019-10-09 21:13 (UTC) (edited on 2019-10-09 21:14 (UTC) by heliochronix)

Hello, First off, thank you for getting this installer working for Arch. It's nice knowing I'm not dirtying up my system with this software.

As to my question. I'm wondering if we can have the packaging process invoke the "install_drivers" script mentioned in the wiki to copy the necessary udev rules into place in the package? It should be as simple as invoking the script "$pkgdir/opt/Xilinx/Vivado/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers/install_drivers" I think.

Also, I had to manually generate the .desktop files for this as per the wiki instructions. Maybe we can package in premade versions of those into this?

xw258 commented on 2019-09-29 06:10 (UTC)

when building: lnx64/jre9.0.4/lib/libawt_xawt.so: libXtst.so.6: can not open shared object file....

libxtst should be added to dependencies.

bcclsn commented on 2019-09-19 19:05 (UTC)

@xiretza: okay, I understand everything... thank you :)

xiretza commented on 2019-09-19 17:07 (UTC)

@bcclsn the point of this is to have a package that can be installed and tracked by a package manager. You can of course just extract it wherever yourself, but at that point there's barely any advantage over using the vendor install scripts directly.

bcclsn commented on 2019-09-19 14:37 (UTC) (edited on 2019-09-19 14:37 (UTC) by bcclsn)

what are the differences between this package and the "WebPACK and Editions - Linux Self Extracting Web Installer"?

can I install this package into an external usb hdd, editing $srcdir and $pkgdir?

thanks in advance

xiretza commented on 2019-06-21 12:15 (UTC)

@GPereira: please build in a clean chroot, the installer is way too much of a mess to run on a dirty system.

GPereira commented on 2019-06-20 12:11 (UTC)

xterm: cannot load font "-Misc-Fixed-medium-R---13-120-75-75-C-120-ISO10646-1"

I get this error and fonts are aliased

« First ‹ Previous 1 .. 9 10 11 12 13 14