Changes
Jump to navigation
Jump to search
yum dnf install make cmake binutils-devel SDL2-devel SDL2_ttf-devel nettle-devel spice-protocol fontconfig-devel libX11-devel egl-wayland-devel wayland-devel mesa-libGLU-devel mesa-libGLES-devel mesa-libGL-devel mesa-libEGL-devel libXfixes-devel libXi-devel
<syntaxhighlight lang=bash>
</syntaxhighlight >
</syntaxhighlight >
===== Arch Linux / Manjaro =====
<syntaxhighlight lang=bash>
<syntaxhighlight lang=bash>
xbps-install -Syu binutils-devel cmake freefont-ttf SDL2-devel SDL2_ttf-devel spice-protocol fontconfig-devel libX11-devel nettle-devel
</syntaxhighlight>
===== Gentoo =====
First set up the necessary USE flags if needed:
<syntaxhighlight lang=bash>
echo "media-libs/libsdl2 gles" >> /etc/portage/package.use/libsdl2
echo "media-libs/nettle gmp" >> /etc/portage/package.use/nettle
</syntaxhighlight>
Then fetch the packages:
<syntaxhighlight lang=bash>
emerge sys-devel/binutils media-libs/libsdl2 media-libs/sdl2-ttf dev-libs/nettle media-libs/fontconfig dev-util/cmake app-emulation/spice-protocol media-fonts/freefonts media-libs/glu
</syntaxhighlight>
This list can also be placed into a setfile in /etc/portage/sets/ so that they can be updated with
<syntaxhighlight lang=bash>
emerge @setfile
</syntaxhighlight>
Either visit the site at [https://looking-glass.hostfission.com/downloads Looking Glass Download Page]
Or pull the lastest '''bleeding-edge version''' using the '''git''' command. '''Note: If you are using the latest bleeding-edge from the master branch you MUST download/use the corresponding host application'''
<syntaxhighlight lang=bash>
git clone --recursive https://github.com/gnif/LookingGlass.git
</syntaxhighlight>
;NOTE: The most common compile error is related to backtrace support this . This can be disabled by adding the following option to the cmake command. '''-DENABLE_BACKTRACE=0''', however, if you disable this and need support for a crash please be sure to use gdb to obtain a backtrace manually or there is nothing that can be done to help you.
Should this all go well you should be left with the file '''looking-glass-client'''. Before you run the client you will first need to configure either Libvirt or Qemu (whichever you prefer) and then set up the Windows side service.
You can call the client from the build directory; or, you can make it callable generally by adding the directory to your path or issuing
<syntaxhighlight lang=bash>
ln -s $(pwd)/looking-glass-client /usr/local/bin/
</syntaxhighlight>
from the build directory.
=== libvirt Configuration ===
If you want clipboard synchronization please see [[FAQ#How to enable clipboard synchronization via SPICE]]
==== AppArmor ====
For libvirt versions before '''5.10.0''', if you are using AppArmor, you need to add permissions for QEMU to access the shared memory file. This can be done by adding the following to ''/etc/apparmor.d/abstractions/libvirt-qemu''.
/dev/shm/looking-glass rw,
=== Qemu Commands ===
'''French:''' "Gestionnaire de périphérique" -> "Périphériques Système" -> "Contrôleur de RAM Standard PCI"
'''English:''' "Device Manager" -> "System Devices" -> "Standard PCI RAM Controller"
A signed Windows 10 driver can be obtained from Red Hat for this device from the below address:
Using IVSHMEM with Scream may interfere with Looking Glass as it may try to use the same device. Please do not use the IVSHMEM plugin for Scream. Use the default network transfer method. The IVSHMEM method induces additional latency that is built into its implementation. When using VirtIO for a network device the VM is already using a highly optimized memory copy anyway so there is no need to make another one.
If you insist on using IVSHMEM for Scream despite it's its inferiority to the default network implementation the Windows Host Application can be told what device to use. Create a looking-glass-host.ini file in the same directory as the looking-glass-host.exe file. In it, you can use the os:shmDevice option like so:
<syntaxhighlight lang=INI>
