Skip to content
frostworx edited this page Dec 5, 2021 · 11 revisions

(Yad Project Page: Yad)

All GUI elements in steamtinkerlaunch use yad (>=7.2)

Several distributions don't have an up2date yad package and/or a yad package maintainer (f.e. debian/ubuntu/mint flavours). If this applies for your distribution you have following options to fix this:

  • (find or be a maintainer for yad for your distribution)
  • compile from source
  • use a custom Yad
  • use exodus to generate a "portable" yad bundle from an other distro which has yad

(for further yad related information [this old discussion[https://github.com/frostworx/steamtinkerlaunch/issues/98] might be interesting)

Compile Yad

Compiling yad from source is not that hard:

  • download the sourcecode from the yad project page, extract it, cd into it

  • install some (build) dependencies and headers (the following example is for ubuntu, adjust the tools accordingly to your distro)

    sudo apt-get install -y automake libtool libglib2.0-dev intltool gtk3++-dev libgtksourceview-3.0-dev libwebkit2gtk-4.0-dev libgspell-1-dev

  • prepare/update the automake build system to match your system:

    libtoolize --copy --force
    autoreconf
    automake --force-missing --add-missing
    intltoolize
    
  • create the Makefile (using the compiler flags from the Arch Linux PKGBUILD, some options ware not required for steamtinkerlauncheamtinkerlaunch) ./configure --prefix=/usr/local --enable-html --enable-icon-browser --enable-html --enable-gio --enable-spell --enable-sourceview

  • compile the program

    make

  • install the compiled program (manual installation usually goes into /usr/local to not conflict with system packages)

    sudo make install

  • (check the installed yad with yad --version)

Custom Yad

steamtinkerlaunch has an option to directly define a yad binary from command line which makes a global/system wide yad installation no longer a hard dependency (won't change the Arch PKGBUILD though)

Valid parameters for <YAD> in steamtinkerlaunch yad <YAD> are:

  • an absolute path to custom binary (f.e steamtinkerlaunch yad /path/to/custom/yad)
  • conty (so simply steamtinkerlaunch yad conty) .If not found the latest Conty release will be downloaded automatically and a yad symlink pointing to it will be defined as yad huge download
  • ai or appimage (so simply steamtinkerlaunch yad ai or steamtinkerlaunch yad appimage) If not found @kadogos appimage from here will be downloaded and defined as yad binary automatically)_ small download (I found out indirectly that this appimage doesn't exit properly, ymmv) If you have no own custom yad binary, and not planning to use Conty as 32bit container, probably simply using steamtinkerlaunch yad ai is the best option, although the used yad version is (currently) not up to date (7.3)
Clone this wiki locally