Package Details: vitis 2025.2.1-1

Git Clone URL: https://aur.archlinux.org/vitis.git (read-only, click to copy)
Package Base: vitis
Description: FPGA/CPLD design suite for Xilinx devices
Upstream URL: https://www.xilinx.com/products/design-tools/vitis.html
Licenses: custom
Conflicts: vivado
Provides: vivado
Submitter: Freed
Maintainer: Freed (ccorn)
Last Packager: ccorn
Votes: 4
Popularity: 0.000198
First Submitted: 2023-04-21 03:30 (UTC)
Last Updated: 2026-04-18 11:46 (UTC)

Dependencies (61)

Required by (14)

Sources (2)

Latest Comments

1 2 3 Next › Last »

jorges commented on 2026-08-22 12:11 (UTC) (edited on 2026-08-22 12:12 (UTC) by jorges)

@ccorn: Thanks for taking the time to answer my question. You've got a point about using directly a supported OS, but there is usually a penalty payed in disk and memory usage, both of which are a premium to me. In the past this approach, fixing the few issues due to arch not being officially supported, has worked well for me, but the tools are getting bigger and more complex. This is not a production machine, just my notebook where I do some basic stuff with these devices.

but out of principle, we do not run a bare makepkg, right? We do not want to risk altering our system just for building some package.

I have to admit that's exactly what I've been doing up to now! But you've hinted a possibly better, safer way that I'll investigate and try to adopt. Thanks again for the info and pointers, they're valuable to me.

ccorn commented on 2026-08-22 01:44 (UTC) (edited on 2026-08-22 01:50 (UTC) by ccorn)

@jorges:

Hi, I have manually installed vitis 2025.2 and I am having some issues. I see some of those might be fixed by this package.

The last time I actually used Vitis (and this package) was years ago. Apart from a handful of manual tests after upgrades, I do not thoroughly verify that this package works as intended. Therefore you might run into "issues" again, though I have fixed the most obvious ones.

So, if getting rid of "issues" is your main concern, I'd suggest that you install distrobox or virtualbox, create a local VM with a supported OS like Ubuntu 24.04.4 LTS, and run the Vitis installer therein.

This also gives you a VM image that you can share with coworkers, which is important because support of specific models might disappear with future software upgrades. Keep the VM image as long as you need the products.

Anyway, if you want to try this AUR package:

  1. I don't have enough space in root, but I do have space in /home. What would be the easiest way to use the available space at /home for the installation?

With makepkg that question does not arise (it uses subdirs of the current working dir by default), but out of principle, we do not run a bare makepkg, right? We do not want to risk altering our system just for building some package.

Therefore, I assume that you use one of the many tools that indirectly use makechrootpkg. By default that uses /var/lib/archbuild for the chroots.

Suppose your build dir is ~/archbuild, then bind-mount ~/archbuild as /var/lib/archbuild:

sudo rm -rf /var/lib/archbuild/*    # remove any previous build chroots
sudo umount /var/lib/archbuild      # in case it's mounted elsewhere
sudo mount --bind -o rw,suid,relatime,xattr,posixacl \
  ~/archbuild /var/lib/archbuild

Edit: Corrected the order of the dirs in the mount command.

  1. Is there a way to choose what components/devices to install? I will only use vitis with one (or two at most) device family. It isn't clear to me from inspecting the PKGBUILD is this is hardcoded or if I can choose.

Consider this line of the PKGBUILD:

sed -i '/^Modules=/s,:0\>,:1,g' "$srcdir"/installer_temp/.Xilinx/install_config.txt

This (supposedly) enables all available modules. I presume that the model defs are a tiny part of the installation, so there is no considerable cost for including them all. If you want to make your own choices anyway, that line is the one to edit.

jorges commented on 2026-08-21 00:36 (UTC)

Hi, I have manually installed vitis 2025.2 and I am having some issues. I see some of those might be fixed by this package. I have a couple of questions, though: 1. I don't have enough space in root, but I do have space in /home. What would be the easiest way to use the available space at /home for the installation? 2. Is there a way to choose what components/devices to install? I will only use vitis with one (or two at most) device family. It isn't clear to me from inspecting the PKGBUILD is this is hardcoded or if I can choose. Thanks

Maaike commented on 2026-02-12 08:55 (UTC)

Thanks, sorry I should have looked into the PKG. I do not have 375GB free space. Will try another way if possible.

ccorn commented on 2026-02-11 16:15 (UTC) (edited on 2026-02-11 17:40 (UTC) by ccorn)

@Maaike: There is no persistent download URL available, therefore you are supposed to download that huge source file yourself, locating it via the Vitis download page and place it beside the PKGBUILD.

From then on, things might go smoothly. However, as the PKGBUILD comment section says:

# No refunds for broken AUR helpers, just use make(chroot)pkg.

Other things to consider: Huge free disk space required. Normally I use a tmpfs filesystem for packaging, but I don't have enough RAM for packaging this hunk of software in a tmpfs. AUR helpers might be affected in the same way. Cf. the comments in the PKGBUILD.

Maaike commented on 2026-02-11 15:11 (UTC) (edited on 2026-02-11 15:12 (UTC) by Maaike)

It is not working unfortunately:

$ yay -S vitis
AUR Explicit (1): vitis-2025.2-1
:: PKGBUILD up to date, skipping download: vitis
  1 vitis                            (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  1 vitis                            (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
==> Making package: vitis 2025.2-1 (Wed Feb 11 16:10:15 2026)
==> Retrieving sources...
  -> Downloading FPGAs_AdaptiveSoCs_Unified_SDI_2025.2_1114_2157.tar...
curl: (37) Could not open file /FPGAs_AdaptiveSoCs_Unified_SDI_2025.2_1114_2157.tar
==> ERROR: Failure while downloading file:///FPGAs_AdaptiveSoCs_Unified_SDI_2025.2_1114_2157.tar
    Aborting...
 -> error downloading sources: /home/.cache/yay/vitis 
         context: exit status 1 


:: (1/1) Parsing SRCINFO: vitis
==> Making package: vitis 2025.2-1 (Wed Feb 11 16:10:16 2026)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading FPGAs_AdaptiveSoCs_Unified_SDI_2025.2_1114_2157.tar...
curl: (37) Could not open file /FPGAs_AdaptiveSoCs_Unified_SDI_2025.2_1114_2157.tar
==> ERROR: Failure while downloading file:///FPGAs_AdaptiveSoCs_Unified_SDI_2025.2_1114_2157.tar
    Aborting...
 -> error making: vitis-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
vitis - exit status 1

mys31f commented on 2025-10-22 23:13 (UTC)

I don't know when it's gonna happen, but AMD's been saying that 2025.2 won't have the single file download option anymore, there's only going to be the unified web based one going forward apparently

ccorn commented on 2025-09-12 20:00 (UTC)

@ercan1102: The launcher script /opt/Xilinx/2025.1/Vitis/bin/vitis has disabled the -new and -classic options available in previous versions, but apparently the Eclipse-based classic IDE remains installed.

The easiest workaround might be to reinstall the previous vitis-2024.2.2 package.

If you are adventurous, you can try reintroducing the -classic option to the current Vitis release. To do that, apply the following patch to the installed /opt/Xilinx/2025.1/Vitis/bin/vitis script:

--- /opt/Xilinx/2025.1/Vitis/bin/vitis.orig 2025-06-12 01:52:21.000000000 +0200
+++ /opt/Xilinx/2025.1/Vitis/bin/vitis  2025-09-12 21:15:47.633141170 +0200
@@ -171,6 +171,7 @@
 OS=`uname -s`

 noSplashPassed=0
+vitisNewOption=1
 defaultGUIOpt=0
 interactiveOption=0
 for arg in "$@"; do
@@ -189,13 +190,9 @@
   elif [[ "$arg" == "-j" || "$arg" == "--jupyter" ]]; then
     interactiveOption=1
   elif [[ "$arg" == "-new" || "$arg" == "--new" ]]; then
-    echo "Error: -new option is not supported by vitis."
-    echo "The default IDE is the new Unified Vitis IDE."
-    exit 1
+    vitisNewOption=1
   elif [[ "$arg" == "-classic" || "$arg" == "--classic" ]]; then
-    echo "Error: -classic option is not supported by vitis."
-    echo "The default IDE is the new Unified Vitis IDE."
-    exit 1
+    vitisNewOption=0
   fi
 done

@@ -247,6 +244,11 @@
   fi
 fi

+if [ $vitisNewOption == 0 ]; then
+   "$RDI_BINROOT"/loader -exec rdi_vitis "${@:2}"   # without -classic (assumed first)
+   exit $?
+fi
+
 if [ -z "$XILINX_VITIS_DATA_DIR" ]; then
   testFile=$HOME/.testFile
 else

You need to install the modified script in /opt/Xilinx/2025.1/Vitis/bin for it to work properly because it uses its path to determine Vitis installation paths.

Then, the following command launches the classic IDE:

/opt/Xilinx/2025.1/Vitis/bin/vitis -classic

This essentially sets up important environment variables and then invokes /opt/Xilinx/2025.1/Vitis/bin/loader -exec rdi_vitis.

However, there is no guarantee that the classic IDE still works as intended. After all, they removed the -classic option for a reason. Anyway, good luck!

ercan1102 commented on 2025-09-12 17:21 (UTC) (edited on 2025-09-12 17:51 (UTC) by ercan1102)

@ccorn: Yes, I am using current release (2025.1). I want to start old Vitis because my university's tutorials contain Vitis 2024.2 (/opt/Xilinx/2025.1/Vitis/eclipse/lnx64.0/eclipse).

I don't know how to set java.library.path other than -Djava.library.path, which isn't working (returns the same error).

I set LD_LIBRARY_PATH to this library folder.

ccorn commented on 2025-09-10 16:34 (UTC) (edited on 2025-09-10 16:35 (UTC) by ccorn)

@ercan1102: Not exactly sure if you refer to the current release.

Anyway, libxv_platform.so is in /opt/Xilinx/2025.1/Vitis/lib/lnx64.o, so you'd have to make sure that your java.library.path contains that.

That's probably not enough. There is a lot of environment setup happening in the usual wrapper scripts /opt/Xilinx/2025.1/Vitis/bin/vitis (which only supports the new Theia-based IDE) and /opt/Xilinx/2025.1/Vitis/bin/setupEnv.sh. You might have to write a similar wrapper script yourself.

1 2 3 Next › Last »