steam-frame/Toastconcern--FrameStudio
1
0 Fork 0
mirror of https://github.com/Toastconcern/FrameStudio.git synced 2026-10-28 20:03:07 +01:00
Code Issues Packages Projects Releases 3 Wiki Activity

docs: a Studio build without a Frame Home payload still builds; releases require one

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ToastconcernandClaude Opus 5.5 committed 2026-10-24 16:40:52 -05:00
1 parent 91d9be5194
commit 7ba59e22c6
1 file changed
+5 -3
Download Patch File Download Diff File Expand all files Collapse all files
docs/building.md
+5 -3
View File
@@ -24,12 +24,14 @@ CMake and Ninja.
studio\build_windows.bat x64
```
Download the `FrameHome-payload` artifact from an Actions run, extract it, and set `FRAME_HOME_PAYLOAD_DIR` to
its payload directory before running the batch file, or [build it manually](#frame-home-payload).
To bundle Frame Home with it, download the `FrameHome-payload` artifact from an Actions run, extract it, and set
`FRAME_HOME_PAYLOAD_DIR` to its payload directory before running the batch file, or
[build it manually](#frame-home-payload). Without one, Studio still builds (CMake warns), but its
**Install on Steam Frame** can't install Frame Home. Release builds (CI) require it.
Use `x86` for 32-bit Windows or `arm64` for Windows on ARM instead of `x64`.
3. The program is `%LOCALAPPDATA%\FrameStudio\build-x64\Frame Studio.exe` (the folder ends in your architecture).
The headset files are copied beside it, in `frame\`.
The headset files, when bundled, are copied beside it, in `frame\`.
To build into another folder, give it as the second argument: `studio\build_windows.bat x64 C:\builds\studio`.