I updated them too, Alex; thanks!
Search Criteria
Package Details: vivado 2024.2-1
Package Actions
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: | 18 |
Popularity: | 0.78 |
First Submitted: | 2019-06-18 22:23 (UTC) |
Last Updated: | 2024-11-27 15:57 (UTC) |
Dependencies (13)
- cpio (cpio-gitAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- inetutils (inetutils-gitAUR, busybox-coreutilsAUR)
- lib32-libpng12
- libpng12
- libxcrypt-compat
- ncurses5-compat-libsAUR
- xorg-xlsclients
- digilent.adept.runtimeAUR (optional)
- digilent.adept.utilitiesAUR (optional)
- fxloadAUR (optional)
- matlabAUR (matlab-supportAUR) (optional) – Model Composer
- qt4AUR (optional) – Model Composer
Required by (12)
- avnet-bdf-git (optional)
- csky-cpu-wujian100-open (optional)
- csky-cpu-wujian100-open-doc (optional)
- csky-cpu-wujian100-open-fpga (optional)
- csky-cpu-wujian100-open-sdk (optional)
- csky-cpu-wujian100-open-simulation (optional)
- csky-cpu-wujian100-open-soc (optional)
- csky-cpu-wujian100-open-test (optional)
- tcl-prompt-git (optional)
- vivado-boards-git
- xrt (optional)
- xrt-bin (optional)
Sources (4)
leuko commented on 2024-11-27 15:50 (UTC)
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.
Sponge_Boi commented on 2024-09-21 19:45 (UTC) (edited on 2024-09-21 19:46 (UTC) by Sponge_Boi)
makepkg
is able to build all parts of the package smoothly and quickly, except for building debug flags. When building debug flags, it has to copy everything over. This makes the package twice the size of what it otherwise would be. It also takes significantly longer to build the package. Please consider disabling the debug
flag in options:
diff --git a/PKGBUILD b/PKGBUILD
index 81da867..a956c42 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -98,7 +98,10 @@ md5sums=(
)
# Takes forever for probably minimal gain
-options=('!strip')
+options=(
+ '!strip'
+ '!debug'
+)
prepare() {
rm -rf "$srcdir/installer_temp"
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 thePKGBUILD
. Refer toPKGBUILD
.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 thisPKGBUILD
.