Arch Linux User Repository

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.

@yuyichao: I understand your usecase, but I'm hesitant to add wrapper scripts to /usr/bin (symlinks aren't enough) - exactly which executables should receive this special handling? Everyone's usecase is probably a little different. Instead, I can suggest creating your own wrappers in /usr/local/bin, which should be on the PATH by default, maybe even with a separate sourced file that defines the current version to make upgrading easier.

sourcing the setting file puts a bit too many scripts on PATH and creating a few wrapper scripts serves as a intermediate level of command line support. It's at least useful in my workflow (not necessarily general I guess) since I launch almost everything for a project from command line but I don't really need more than the "default programs" that have the associated desktop entry.

@yoyichao: ah, thanks, I hadn't noticed the SDK disappearing. I applied the change locally, but since it only removes a useless file, I won't push a package update yet (the cost for users of either rebuilding or ignoring the package is greater than the benefit imho). As for putting binaries on the path - that's exacatly what those shell scripts are for. If you want the tools to always be on your path, source /opt/Xilinx/Vivado/2019.2/settings64.sh in your shell's init script (e.g. .bashrc).

Edit: oh, and regarding the update: I'd rather not package those unless absolutely necessary, it would increase the build time even more with no benefit for most users. This also aligns with Xilinx's update recommendations.

The SDK is gone in the 2019.2 version so the corresponding desktop file can be deleted.

It'll also be nice to allow execution from command line as well. Based on the desktop file, a symlink like ln -s /opt/Xilinx/DocNav/docnav "$pkgdir/usr/bin/xilinx-docnav" should work for docnav while vivado need a shell script like

#!/bin/bash

unset LANG
unset QT_PLUGIN_PATH
. /opt/Xilinx/Vivado/%VERSION%/settings64.sh
exec /opt/Xilinx/Vivado/%VERSION%/bin/vivado "$@"

There also seems to be an updator from December, any idea it can be packaged as well?

@schui: hm, haven't come across anything like that yet. It might be quickest to work this out via IRC, feel free to message me (user lambda on freenode).

@xiretza Oh, my fault. The build process was successful. Thank you!

Unfortunately the application via .desktop nor the shell file doesn't start. The error message: execvp: Exec format error. After some googling I don't find any clue how to fix this. I really need this software for a student project. I'm running Linux 5.6.5-arch3-1 with KDE 5.69.0 / Plasma 5.18.4. Thanks for any advice!

@schui: as the source= suggests, it's a local file. Read the notes in the PKGBUILD, you need to download it yourself because it's locked behind a login wall.

@xiretza Great package, thank you! Can you please update the PKGBUILD? One url is probably broken. ==> Validating source_x86_64 files with sha256sums... digilent.adept.utilities_2.3.2-amd64.deb ... Passed ==> Making package: vivado 2019.2-3 (Tue 21 Apr 2020 11:00:26 AM CEST) ==> Retrieving sources... -> Downloading Xilinx_Vivado_2019.2_1106_2127.tar.gz... curl: (37) Couldn't open file /Xilinx_Vivado_2019.2_1106_2127.tar.gz ==> ERROR: Failure while downloading file:///Xilinx_Vivado_2019.2_1106_2127.tar.gz Aborting... Error downloading sources: vivado

@ccorn those changes all seem reasonable (no idea how the wrong checksum sneaked in there - and how I never noticed it before). Building it right now, will push once that's succeeded.

I have made three changes to the PKGBUILD:

1. For unknown reason, I had to fix the md5sum for Xilinx-DocNav.desktop.
2. Re-enabled compression because the new default (zstd) is quite fast, particularly if multithreading is enabled (at least on my dual-Xeon workstation)
3. At the end of package(), delete the unpacked source tree to save space for subsequent packaging and checks.

The latter two changes enable builds within 72GiB chroot capacity. On my workstation, this means that I can still use a tmpfs mount for that.

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -55,10 +55,10 @@ md5sums=('e2b2762964ef5f014591b13d77d823ab'
          '69d14ad64f6ec44e041eaa8ffcb6f87c'
          'b7cad6d39ef5293d4f433b8c9959f486'
          '44bb51e1c8832f001cb7d21b90cb5796'
-         '40d60bc80129f8e7fe7df56ec2605ebf')
+         '4d37975f586923ad02a50056ff569703')

 options=('!strip')
-PKGEXT=".pkg.tar"
+#PKGEXT=".pkg.tar"

 prepare() {
    # https://git.archlinux.org/pacman.git/commit/?id=349c22d043290ccd0cce9f30981f5415e295442a
@@ -97,5 +97,9 @@ package() {
    # clean up artefacts, remove leading $pkgdir from paths
    rm -rf "$pkgdir/opt/Xilinx/.xinstall/"
    find "$pkgdir/opt/Xilinx/" -name '*settings64*' -exec sed -i -e "s|$pkgdir||g" '{}' \+
+
+   # Save space for subsequent packaging, checking etc
+   cd ..
+   rm -rf "Xilinx_Vivado_${pkgver}_${_more_ver}"
 }