Closed CurryKitten closed 4 years ago
Done, but not committed yet (until I also make 0.49b live) else every single platform will break :) The before list looks like -
CK-FPV-Sim-Mac-Steam-048b.app/Contents/MacOS/CK-FPV-Sim-Mac-Steam-048b
CK-FPV-Sim-Win64-Steam-048b\CK-FPV-Sim.exe
CK-FPV-Sim-Win32-Steam-048b\CK-FPV-Sim.exe
CK-FPV-Sim-Linux64-Steam-048b.x86_64
CK-FPV-Sim-Linux32-Steam-048b.x86
...and the after
CK-FPV-Sim-Mac-Steam.app/Contents/MacOS/CK-FPV-Sim-Mac-Steam
CK-FPV-Sim-Win64-Steam\CK-FPV-Sim.exe
CK-FPV-Sim-Win32-Steam\CK-FPV-Sim.exe
CK-FPV-Sim-Linux64-Steam.x86_64
CK-FPV-Sim-Linux32-Steam.x86
As long as it all works, it should make any future versions easier to handle.
In each of the Stream builds, I have to define a launch path, based on Steam deploying the zip file, so for the 048b version of windows64 the launch path is
CK-FPV-Sim-Win64-Steam-048b\CK-FPV-Sim.exe
The problem with this is that every time I update the release I then have to go through every launch path and update that as well. I managed to make a typo on the last release leaving Windows broken for about an hour - so for Steam I'll remove the version numbering from the package so I can keep a consistent launch path. So for the windows build above it would change to -
CK-FPV-Sim-Win64-Steam\CK-FPV-Sim.exe
I'm not worried about people not knowing exactly what they are running as Steam keeps it up to date, and you'd have to go off on a search to find the actual executable.