Install instructions for customised Vivado AUR package

README.md

You don't actually have to download the entire (now over 100 GiB) unified installer.

The self-extracting web installer (~300 MiB) can create a customised bundle identical to the unified installer - thus only downloading the components you require. Here's what I did to install Vivado and support for Artix 7 only, so no guarantees that this works in general. Keep in mind that version numbers and dates may have changed.

1. Download the “AMD Unified Installer for FPGAs & Adaptive SoCs 2023.2: Linux Self Extracting Web Installer”
   • This is a binary with a name like FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256_Lin64.bin
2. Create the archive
   1. Run the installer (chmod +x the binary and launch it from a shell)
      • Flags to the installer binary must be provider after -- so as to not pass them to the makeself wrapper
      • Passing the --xdebug flag to the installer binary has helped debug weird issues in the past, so may be worth using
   2. Provide AMD account credentials
   3. Select “Download Image (Install Separately)”
      • To make creating the .tar.gz easier, name the final directory in the download path FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256 (this matches the expected folder and filename in the PKGBUILD)
      • Ensure “Download files to create full image for selected platform(s)” is set to “Linux”
      • Under “Image Contents”, select “Selected Product Only”
   4. Proceed through the installer as normal, selecting only the product and components required
   5. Once the download has finished, use tar -cvf FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256{.tar.gz,} to create an archive identical to the unified installer
      • The archive must contain a folder named FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256 which holds the xsetup binary
3. Build the package
   • Follow the instructions contained in the PKGBUILD, substituting the unified installer with the newly created .tar.gz file
   • As the archive has changed, pass --skipchecksums to makepkg when building

Although executing the installer within the package build took only 2 minutes, the process of linting and compressing took a significant amount of time.