Archives
/
GlosSI-fork
mirror of https://github.com/Thracky/GlosSI
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
master_legacy
gh-pages
experimental
v2
UWP_Overlay
2.0.8
1.0.0
1.0.1
1.1
1.1.2
1.2.0.15
1.2.1.18
1.2.1.20
1.2.2
1.2.3.35
1.2.4
1.3.0
1.4.0.68
1.4.1.87
1.4.2
1.4.2.108
2.0.0.117
2.0.1.124
2.0.5
2.0.5.139
2.0.6
2.0.7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5c16b4a065'
${ noResults }
GlosSI-fork/Build_Install.md

1.3 KiB
Raw Blame History

Building GloSC

Build requirements:

ViGEms user mode library as well as SFML are bundled in the repo. For ViGEms installation refer to the Readme-files from the relevant sub-projects, or use the binary installer (if available).

--

Set the correct Qt version for "GloSC", "GloSC_GameLauncher" and "SteamTarget" depending on your build.

Rebuild the solution and you should be good to go.

Installation

Copy all files out of the relevant build directories, as well as, "TargetConfig.ini" and the relevant SFML, ViGEmUM and QT .dll-files in a separate directory.

To launch games without doubled overlays, GloSC_GameLauncher has to run at boot. If you didn't use the installer, just place the reg-entry for the autostart

Be careful that the right executable is running, as there can only ever be one Instance of "GloSC_GameLauncher" running.

Afterwards create your shortcuts with GloSC and you are ready to go.

Notes:

The GloSC_GameLauncher must be running from that directory, as Admin, to make double sure Steam does get unhooked after closing a shortcut