| 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, vivado |
| Submitter: | xiretza |
| Maintainer: | VitalyR (leuko) |
| Last Packager: | leuko |
| Votes: | 19 |
| Popularity: | 0.72 |
| First Submitted: | 2019-06-18 22:23 (UTC) |
| Last Updated: | 2025-02-03 22:03 (UTC) |
Good catch Alex, thanks!
Your idea makes sense. Now, vitis_ provides vivado and will conflict with other packages that provide vivado or vitis. vivado provides vivado and will conflict with other packages providing vivado.
I did not increment the version to save CO2, please rebuild if you need this update. I could not test it, feedback welcome.
The package_vitis_ function still has a hardcoded 2024.1 version in some places, which causes it to fail.
It would also be useful to add vivado to the provides of vitis_, so other packages that depend on vivado can be used when we have vitis installed via this package.
sed -i \
"s|\$CUSTOM_LIBRARY_PATH|$_installprefix/Vitis/2024.1/tps/lnx64/cmake-3.24.2/libs/Ubuntu|g" \
"$pkgdir$_installprefix"/Vitis/2024.1/bin/vitis
sed -i \
"s|\$MY_LIBRARY_PATH|$_installprefix/Vitis/2024.1/tps/lnx64/cmake-3.24.2/libs/Ubuntu|g" \
"$pkgdir$_installprefix"/Vitis/2024.1/bin/vitis
Update on the fonconfig "bug". The issue is fixed with the now available fontconfig 2:2.16.0-2.
@Lacsapix, thanks for the heads up. The fix appears to work for me as well. I assume you were encountering an issue where it would crash from a grey splash too?
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
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.
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?
For anyone using HiDPI screens: setting QT_AUTO_SCREEN_SCALE_FACTOR=1 will make DocNav display correctly.
I updated them too, Alex; thanks!
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.
Pinned Comments
leuko commented on 2024-01-14 21:14 (UTC) (edited on 2024-09-26 06:41 (UTC) by leuko)
PKGBUILDcannot download Vivado, you have to download Vivado before executing thePKGBUILD. Refer toPKGBUILD.This
PKGBUILDis 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 thisPKGBUILD.