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: 19
Popularity: 1.06
First Submitted: 2019-06-18 22:23 (UTC)
Last Updated: 2024-11-27 15:57 (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

1 2 3 4 5 6 .. 15 Next › Last »

Lacsapix commented on 2025-01-20 11:50 (UTC)

There is a bug (I think) when upgrading fontconfig to 2:2.16.0-1. Downgrading to 2:2.15.0-2 works for now. https://archive.archlinux.org/packages/f/fontconfig/fontconfig-2%3A2.15.0-2-x86_64.pkg.tar.zst

leuko commented on 2024-12-31 08:11 (UTC) (edited on 2024-12-31 08:15 (UTC) by leuko)

This is a good idea, I just have been reluctant to do this because of the complexity, e.g., I don't want to test the effects on non-KDE or non-Wayland environments.

I would also like to merge QT_AUTO_SCREEN_SCALE_FACTOR with https://wiki.archlinux.org/title/Xilinx_Vivado#Vivado_shows_an_empty_screen_on_Sway

I use Sway, but I don't have Docnav. Can someone with KDE and someone else with X11 try the following line on Vivado and Docnav?

Without _JAVA_AWT_WM_NONREPARENTING you see a blank Vivado window on Sway.

/usr/share/applications/Vivado 2024.2.desktop:

...
Exec=bash -c '[ "$XDG_SESSION_TYPE" = "wayland" ] && export _JAVA_AWT_WM_NONREPARENTING=1 QT_AUTO_SCREEN_SCALE_FACTOR=1; exec /opt/Xilinx/Vivado/2024.2/bin/vivado'
...

After the test I can merge these.

Poscat commented on 2024-12-30 03:05 (UTC)

Hmm I think you need to set QT_AUTO_SCREEN_SCALE_FACTOR in the .desktop file if you are on KDE since it will overwrite this environment variable. Any chance of patching it in PKGBUILD @leuko?

Poscat commented on 2024-12-29 06:05 (UTC)

For anyone using HiDPI screens: setting QT_AUTO_SCREEN_SCALE_FACTOR=1 will make DocNav display correctly.

leuko commented on 2024-11-27 15:50 (UTC)

I updated them too, Alex; thanks!

Alex commented on 2024-11-27 14:02 (UTC)

With Vitis 2024.2, the install_config-vitis.txt config does no longer work. I freshly generated the config file and had to replace the old Modules= line with

Modules=Install Devices for Kria SOMs and Starter Kits:0,Vitis IP Cache (Enable faster on-boarding for new users):0,Versal AI Edge Series ES1:0,Zynq-7000:1,Virtex UltraScale+ 58G:0,Versal Gen 2 AI Edge Series:0,Artix UltraScale+:0,Spartan-7:1,Install devices for Alveo and edge acceleration platforms:0,Spartan UltraScale+:0,Vitis Networking P4:0,Kintex UltraScale+:0,Versal AI RF Series ES1:0,Artix-7:0,Zynq UltraScale+ MPSoC:0,DocNav:0,Versal HBM Series:0,Virtex UltraScale+:0,Kintex-7:0,Versal AI Core Series:0,Versal AI Edge Series:0,Virtex UltraScale+ HBM:0,Kintex UltraScale:0,Versal Gen 2 Prime Series:0,Versal Premium Series:0,Virtex UltraScale:0,Zynq UltraScale+ RFSoC:0,Power Design Manager (PDM):0,Versal AI Core Series ES1:0,Versal Prime Series:0,Virtex-7:0,Engineering Sample Devices for Custom Platforms:0

I did not test, if the config for vivado works.

leuko commented on 2024-11-15 09:29 (UTC)

Thanks @poscat. The default setting is indeed debug. I updated the PKGBUILD.

Poscat commented on 2024-11-15 06:37 (UTC)

The default settings is in fact not !debug. Yes debug won't increase binary size but It slows down the packaging time by A LOT.

leuko commented on 2024-09-24 20:21 (UTC)

@Sponge_Boi, thanks for your suggestion about temp files. This has been bugging me too :) I integrated your suggestion.

But I cannot confirm your suggestion about !debug. Just to be sure I repackaged with !debug and did not see any difference in package size. In my opinion !debug should be part of the global makepkg.conf. Moreover the default setting is !debug as I know.

I made also the following changes to the PKGBUILD:

  • I believe most people do not want to install all features because of the large size. I made configuration per install_config-*.txt as default and made these templates part of the repo.
  • I added patches to fix the Python virtual environment that the Vitis Unified editor uses. I created a split package for Vitis so these patches are separated from the Vivado package. I left pkgname as (vivado) so that unexperienced users can avoid making both Vivado and Vitis packages at the same time.

Sponge_Boi commented on 2024-09-21 20:30 (UTC) (edited on 2024-09-21 20:31 (UTC) by Sponge_Boi)

When started, Vivado creates log files in whichever path it starts in without deleting them. The desktop entry does not specify a path, so more often than not, $HOME gets filled up with vivado*.log and vivado*.jou files. I suggest we add Path=/tmp to any desktop files created in /usr/share/applications/ in order to stop log files from bloating up the home directory and to make log files get wiped on boot.

1 2 3 4 5 6 .. 15 Next › Last »